Is there any way (even manually through mysql) to reset all node_access_byrole permissions? Mine have gotten corrupted somehow, denying view to all; it may be simpler to re-set the dozen or so I need to not-read than to reset hundreds to allow read.
Is there any way (even manually through mysql) to reset all node_access_byrole permissions? Mine have gotten corrupted somehow, denying view to all; it may be simpler to re-set the dozen or so I need to not-read than to reset hundreds to allow read.
Comments
Comment #1
Zed Pobre commentedBumping to critical and moving to code, because I've just had this happen to me as well, and it's becoming a nightmare to fix. Somehow, when first installing node_privacy_byrole, not all of the nodes (in fact, very few) had their entries created into the node_access table, resulting in a mass lockout from the site. I manually went through a few entries to get minimal functionality back working again, but I wasn't even able to disable the module. If I used settings to inactivate the module, then unchecked it in the modules config page, all non-admin access to the site was lost, completely. Upon initial install, node_privacy_bynode *MUST* grant view permissions to all nodes, and *MUST* check to see if it was inactivated and reactivated later, to see if nodes were created when it was deactivated that it needs to install basic view permissions for all roles.
Installing this module is a very good way to completely incapacitate your site. User beware!
I'm working on an SQL command to insert anonymous view access for all nodes, but it'll take me a while to think about. I'll post back with it when I finish.
Comment #2
Zed Pobre commentedOkay, the following appears to work to grant anonymous and authenticated users view access to all nodes that did not have entries created:
As a warning, this will reset permissions on ALL NODES for anonymous and authenticated users to be viewable but not editable/deletable, so if you had set up custom permissions for a few nodes, you'll have to go back and do it again.
Comment #3
Zed Pobre commentedUnfortunately, it seems that node_access is also plagued by the term node count bug, so this has only replaced my original problem with a new one.
Comment #4
jack_of_spades commentedNote that my original problem was on MySQL not pgsql, which may mean we had a different set of issues.
Comment #5
jondoesdrupal commentedTidying up old issues. Focus now is on Drupal 5 version of the module. If there is still demand for this to be resolved and it gets resumbitted then I'll look into finding a solution.