The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.I think nodeaccess is misbehaving all of a sudden...not sure tho. I installed it a long time ago and never really used it but didn't get rid of it. I've updated it along the way just to keep my status_update clear. I did some other updated to my modules the other day (but not nodeaccess) and now all non-admin users can't see MOST old (older than a day old) content...well some content...pages are OK, events, classifieds, and all cck node types are not viewable. New ones I create are viewed OK.
I seem to recall having troubles in the past getting rid of nodeaccess...there doesn't seem to be an uninstall. Today, I tried, disabling it, deleting the module over FTP and dropping the table manually from MySQL but that gave access denied errors on all the pages (the ones that were working). Thankfully I took a backup of the node_access table.
It is the only access related module I have in operation on my site and this is why I think it's causing a problem.
How can I find out for sure?
How can I delete the module properly and any access restrictions it is causing?
Or, if I keep it (if I have to), how can I change permissions of all existing content so all roles can view it?
Comments
Comment #1
mdowsett commentedSo it is nodeaccess....but it's behaving....doing what it's supposed to do. Strange that it's just kicked in after being there for about 8 months.
How do I get rid of it (without messing up access to all the nodes). I've run an SQL script to add access for all nodes for anon users so they are all accessible now.
Comment #2
mantyla commentedThis is the combined result of a bug and bad luck. Because of a critical bug, Nodeaccess doesn't give any rights to new nodes, leaving them at defaults. Because of this, everything remained fine for a long time, even though the whole time the Nodeaccess defaults should have denied access to nodes of types other than page. Saving the admin settings, enabling or disabling the module will cause the access rights to be rebuilt, so if you did any of those, it would have caused those nodes to disappear. Another module may also have triggered the rebuild.
The good news is that Nodeaccess does have a working uninstall. You need to disable the module first to be able to run it. Just disabling it should be enough though: it triggers the rebuild, and while Nodeaccess would be disabled all nodes would revert to their defaults: view for all.
And don't, don't try to delete the node_access table! It is not part of this module, but is required by Drupal core.
Comment #3
mdowsett commentedthx - I found out the hard way about the node_access table being required. Thank gawd for backups!
Comment #4
mdowsett commenteddisabling the module doesn't reset (ie remove) all access restrictions...should it? Is there anything you have to do?
Or does that happen when you "uninstall" it?
Comment #5
mdowsett commentedi still can't get rid of this module. It's causing serious access problems with my site (especially since I have now installed og).
I've upgraded it to 1.2 hoping that it'd let me uninstall it. But when I uncheck the module, it takes me to the /admin/build/modules/list/confirm page....but it gives me a blank white screen! no errors. no hints as to what is going on.
And when I refresh the /admin/build/modules/ page, it shows the nodeaccess module as enabled still.
I've manually dropped the nodeaccess table from the database but that doesn't fix my issues either.
Comment #6
mdowsett commentedI found out the blank white screen was due to lack of php memory.
I found and followed this and it saved me. I suppose I have too many modules installed but increasing the php memory allowed me to successfully disable the nodeaccess module and then uninstall it properly.
Then everything worked!
Comment #7
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.