Would be very nice to provide a Ctools and Views access plugin so that pages can be restricted by a user's assigned section.
The idea is that a View or a Page Manager object can be assigned to a section and only users who can access that section can view the item.
E.g. I don't think a Node context is required or desirable here. Just a user context. We want to be able to create 'node-like' access to Ctools objects.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 1089330_Adding_a_ctools_access_plugin_for_workbench_access_3_D7.patch | 4.82 KB | stevector |
Comments
Comment #1
stevectorI agree that this is a good idea. Here are some other tickets involving CTools/Workbench integration.
#1103638: Task plugin for 'admin/workbench'
#1108502: Allow modules to alter the list of possible next states
This issue is not a duplicate because this issue is specific to Workbench Access.
Comment #2
agentrickardRight, and access plugins are a different thing, too, and can be implemented without introducing dependencies.
Comment #3
stevectorHere's a patch that creates an access plugin. It uses workbench_access_node_access() to check if a user has access to edit a node. This is somewhat a proxy for workbench_access_check(). agentrickard do you have an opinion on this?
Comment #4
agentrickardIt occurs to me that since sections are only assigned nodes, these plugins make less sense. The idea is that a View or a Page Manager object can be assigned to a section and only users who can access that section can view the item.
Is that how this is implemented?
E.g. I don't think a Node context is required or desirable here. Just a user context. We want to be able to create 'node-like' access to Ctools objects.
That was my original intent, which I don't think I made explicit in this issue.
Comment #5
robeano commentedThis is a nice feature but apparently no one is clamoring for it just yet. Lowering priority.
Comment #5.0
robeano commentedAdding more detail to the Description