I have the following scenario:

* Editor Role should not be allowed to delete nodes. Therefore the corresponding permission is de-selected in the permissions page.
* However Editor should be able to to delete nodes from Views Bulk operations. Using Rules an action is created called "safe delete" that checks things like if the node is not published etc. before deleting the node.
The problem is the Views Bulk Operations respects Node Access. Editor will not be able to delete the node as he has not been given that permission. Is there a way that Editor can become a higher role user (as sort of sudo) while performing that action in VBO? Alternatively is there a way to tell VBO to ignore node access for this action?

I'm sure this is a mainstream requirement but I can't seem to find a solution.

Solutions which do not involve programming will be preferred

Comments

sidharth_k’s picture

Component: Rules Core » Rules Engine

Please note that form_altering delete out from the node edit form is not a viable option as user can always delete a node (if s/he has delete priviledges) using the URL /node/[nid]/delete

BTW this question was filed at stackoverflow.com ( http://stackoverflow.com/questions/3690519/do-not-allow-a-user-to-delete... ) also... however no one seems to have been able to answer this.

Thought the Rules maintainers might be able to give a definitive answer. Hence posting here.

TR’s picture

Component: Rules Engine » Rules Core
Issue summary: View changes
Status: Active » Closed (outdated)

Looks like you got some answers on stackoverflow.