Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I am wondering if leveraging views would help the workspace module become more feature rich? Perhaps workspace can simply become a filter for views? See http://drupal.org/node/243215#comment-909334 for my views support request.
| Comment | File | Size | Author |
|---|---|---|---|
| #13 | interdiff-278906-9-13.txt | 449 bytes | phenaproxima |
| #13 | 278906-13.patch | 1.83 KB | phenaproxima |
| #9 | interdiff-278906-8-9.txt | 1.06 KB | phenaproxima |
| #9 | 278906-9.patch | 1.76 KB | phenaproxima |
| #8 | 278906-8.patch | 603 bytes | phenaproxima |
Comments
Comment #1
webchick+1 for this feature. I was sad that this module isn't a bunch of default views. :(
Comment #2
Frank Ralf CreditAttribution: Frank Ralf commentedHi bomarkmonk,
This sounds like a very good idea. But IMO Workspace should still provide its functionality as a lightweight standalone module even without Views.
More feedback from other users welcome!
tia
Frank
Comment #3
bomarmonk CreditAttribution: bomarmonk commentedHere is a related discussion about views: http://drupal.org/node/243215
Workspace could become a robust views filter with a default view that works like the existing workspace page, then the workspace module itself might require much less maintenance. Views is pretty universal these days, but there might be a Drupal site out there that would use workspace, but not views. I'm not sure how realistic that possibility actually is. Just adding my two cents here, but I'm not a developer myself, so take my suggestion with a grain of salt :)
Comment #4
Frank Ralf CreditAttribution: Frank Ralf commentedThanks for the feedback! Actually I have a Drupal site out there with no Views (yet). It's a primary school website and I want to keep it as simple as possible for to keep it manageable even for not so tech savvy teachers. But I will keep your suggestion on the list.
However, IMO the scope of the Workspace module should be kept restricted to the user's own content. Extending it to other user's content as suggested in #243215: Filter Content to what the Current User can Edit is already handled by modules like http://drupal.org/project/workflow
Cheers,
Frank
Comment #5
jvandyk CreditAttribution: jvandyk commentedHere's a workspace-style view replicated in Views. What it does not do is
- have the Content and Attachment tabs (you could do this with an additional Attachment view and the menu tab settings in views)
- have the "Add new item" header; I imagine you could do this with a very creative views header
- have the Operations column (you could probably do this with http://drupal.org/project/views_bulk_operations )
- have the menu item for "My workspace"; it uses http://example.com/content/2 for user 2's content via views arguments
Comment #6
bomarmonk CreditAttribution: bomarmonk commentedFantastic; I'll have to test this out!
Comment #7
Frank Ralf CreditAttribution: Frank Ralf commentedJust changing status to indicate the current state of the affair ;-)
Comment #8
phenaproximaArise, Lazarus!
This patch should expose Multiversion's Workspace entity type to Views generically. This probably could use some tests, but it's a start.
Comment #9
phenaproximaOkay...added a really, really basic test.
Comment #13
phenaproximaMaybe now?
Comment #14
josephdpurcell CreditAttribution: josephdpurcell at Digital Bridge Solutions for Acquia commentedI was able to validate that you can create a view of Workspace entities. I agree with the test as well--since it's using EntityViewsData and there are already tests for that, just testing it shows up should be a good proxy for checking all functionality provided by it works.
Setting to RTBC.
Comment #16
jeqqComment #17
jeqqThank you!