Closed (won't fix)
Project:
Views Bulk Operations (VBO)
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
8 Dec 2010 at 14:00 UTC
Updated:
22 Sep 2011 at 11:08 UTC
Jump to comment: Most recent file
Comments
Comment #1
infojunkie* Does this happen with other actions too?
* Is actions_permissions.module enabled?
Comment #2
odegard commentedThanks for replying!
* If I enable the other actions available in the VBO view, they show up fine for editor. It's just the ones I created.
* Actions_permissions is enabled and configured.
It's so weird, that 1) the actions work for admin, so there's nothing wrong with the rule, and 2) they show up in the permission table along with all the others, but still they don't show up in the view.
Perhaps there's a bug when VBO checks for permissions when it *renders* the form? I gave editor all permissions available, but that didn't work.
Comment #3
lewie6 commentedi have the exact same problem.
any suggestions?
Comment #4
odegard commentedI ended up making my own module based on one of the existing rules. I have 3 content types and an additional problem was showing and sorting three cts in one view. The module below fetches emails from one ct at a time.
Here it is, hope it is of help:
(hent epost = fetch emailaddresses)
hent_epost.info
hent_epost.module
Comment #5
bojanz commentedIs this still a problem with latest 6.x-1.x-dev?
Comment #6
larowlanYes, also affects 7.x-3.0-beta2. Do you want me to create a new issue against D7 branch or move this one?
I've got a feature that will reproduce this if that helps.
Happy to go debugging if you can point me in the right direction.
Comment #7
bojanz commentedHello larowlan,
I'm looking forward to finally catching this bug :)
Please do post the feature.
Are you using actions_permissions? Does this happen only for core actions? Rules are fine?
Access (whether the action gets shown at all in the dropdown) is determined by the "access" method of the operation plugin. So for core actions that's ViewsBulkOperationsAction::access() (action.class.php).
The body of the method is small so you should be able to get a lot of insight with a few dsm()s.
Comment #8
larowlanHi
It's only for rules, and no I don't have actions_permissions enabled.
If I modify the rules component class as follows:
ie so it only returns TRUE, then it works - so it's in the rules_action function where the issue exists.
Feature attached, hopefully it's stand alone.
Lee
Comment #9
bojanz commentedThen the bug is on the Rules side, let's continue in the Rules queue: #1217128: limiting Rules components to specific permissions.
Restoring status for the 6.x-1.x bug.
Comment #10
hnln commentedsame problem (D7 with both action_permissions enabled and disabled), the rules issue suggest that VBO bypasses rules access for the moment.
Comment #11
bojanz commentedI've committed a workaround for D7 rules (made access() always return TRUE).
Closing the D6 issue since there hasn't been any info since february.