Posted by larowlan on June 30, 2011 at 3:16am
3 followers
Jump to:
| Project: | Subuser |
| Version: | 7.x-2.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs work |
Issue Summary
As detailed in #1195720: Add note to README about backwards compatibility (style plugin -> field) - views_bulk_operations were changed from a style plugin to a views form field.
The default views need to be updated for this to work otherwise the user/%/subuser path returns a 404 error.
Attached patch updates the views.
| Attachment | Size |
|---|---|
| VBO-no-longer-a-style-plugin.patch | 11.37 KB |
Comments
#1
Patch applied and the view is working correct now.
Don't forget to apply also the save_relation fix or no relation will be created. #1208314: Relation is never saved
#2
2 notes:
1.) The above works fine with Relation 7.x-1.0-beta3 - but not with the latest -dev version. Be warned.
(I haven't checked which commit broke things, but seeing the description, it's probably http://drupalcode.org/project/relation.git/commit/e8e00ad from yesterday. Maybe boombatower can ask solotandem what needs changing ;) )
2.) I am able to execute VBO operations for which the user does not even have permissions! (For instance, I can add any role to my subusers, using the VBO stuff.)
That's got nothing to do with the subuser module per se... I've seen it happen on another one of my sites as well. I'm just warning people.
(It's probably VBO which is still in alpha state.)
So for now, I just deleted the VBO operations field from the view on my live site. I'm not going to test this any further at the moment. I'd love to hear from someone, if they also/do not see this behavior and are able to do actions 'beyond their privileges'.
#3
changing title to reflect why I changed status.