Posted by saulelis on January 9, 2013 at 1:49pm
3 followers
| Project: | Domain Access |
| Version: | 7.x-3.7 |
| Component: | - Domain Content |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
When a user accesses Affiliated content list in my site, the Update options widget is not available for him. The collapsible AFFILIATE PUBLISHING OPTIONS tab is there and all the checkboxes there are active, but there is no list of update options and no Update button. I've given the the user ALL permissions of Domain access and Domain Content - without desired results. The only thing that does work is giving the user the Administer content permission - but I don't want to do that for obvious reasons.
Has anyone else encountered a similar problem? I'm at a loss as to where to begin looking for the problem. Could it be a wrong combination of permissions or a conflict with other modules?...
| Attachment | Size |
|---|---|
| Screenshot-1.png | 35.49 KB |
Comments
#1
You would have to use a custom form_alter() to change that behavior, since it's by design (and based on the batch actions provided by core).
Since hook_node_operations doesn't enforce any access controls on its own, that permission check is the only one we really have.
Now, there is a possible argument that we should allow access to domain-module specific actions. And I notice that domain_content_filter_operations() is now calling a variable setting that we removed when we added content-type specific settings.
So perhaps that's the cleanup needed here. However, users without "Administer content" still won't have access to all batch operations.
#2
And a patch.
#3
Cool patch, mate! Works perfectly and this is exactly what I was looking for. I didn't mean to imply that all node batch operations should be there. We only need domain-module specific ones in this form.
#4
Yeah, and this change makes sense to me as well.
#5
Committed.
e9798d5..295aa2c 7.x-3.x -> 7.x-3.x#6
Wrong status.
#7
Automatically closed -- issue fixed for 2 weeks with no activity.