Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By jonashogstrom on
Hi. I have a site under development. All content that I have created up till now has been accessible by anyone, no need to log in. The other day drupal started to act really weird. Any page that I create becomes restricted to admin users. Old pages that have been accessible by anonymous users become restricted as well when I modify them.
A few days ago, I installed the UpdateModule module and then I installed updates to 5-6 modules. Including cck, and views (to 1.6 beta4). The upgrade did not run flawless, there were some messages, but at the time, they did not seem like they needed any attention, and the site has been running well while logged in as admin.
I can't find any setting for my pages that would indicate that they should be restricted to certain users (there are no "roles-settings" when I edit pages).
If anyone has any clues (or further questions to narrow the problem down), I'd be most grateful.
/Jonas
Comments
...
Any installation error messages can indicate a problem which is why they should be investigated.
Installed 5-6 modules? Any permissions based modules? Did you have any before? Most of the time this is the result of permissions based modules.
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
Yes, I do feel a little
Yes, I do feel a little stupid that I didn't copy the log messages to a safe place (sounds like a feature suggestion, have the upgrade error messages emailed to site admin).
Here is a list of recently installed/upgraded modules:
scheduler
googleanalytics
bloginfo
gsitemap
userlink
cck
jstools
linktocontent
views
phpbb
does any of those strike you as suspicios. They were all installed/upgraded to the latest version from drupal.org.
what exactly is a permission based module?
I did some testing with a dummy user. When the user has no additional roles, he will not be allowed to watch the restricted pages. If I give the user the custom role "Founder", he will be allowed to see the pages. Having only the admin role is not good enough, only the "Founder" role grants permission to see the pages.
I have gone through the Access Control list several times to make sure that all settings are as they should, and it seems to me that they are. I have granted "access content" to anonymous (and old pages, that have not been modified since things started to get screwed up, are still accessible by anonymous users and any logged in user as well). Is there anything else in particular that I should check in the Access Control list?
/Jonas
I started digging into the
I started digging into the mysql database and found that all the "broken" pages are missing from the node_access table.
Adding that row manually in the db will give access to logged in users, but not anonymous users. Atleast I'm a small step closer.
/Jonas
Really strange. It turns out
Really strange. It turns out that about half of the pages I fixed by inserting a row in the node_access table are visible for anonymous users, the other half still gives "access denied". All the "fixed" pages becomes visible for logged in users (even with no extra privileges). Is there some caching involved here?
/Jonas
Must have been caching...
Must have been caching... the pages that I "fix" manually in the db by adding a new row in node_access will work for all users (including anonymous) eventually.
I took a snapshot of the database and diffed before and after modifying a page. the most significant is the removal of the row in node_access, the rest seems to be related to caching and updating last-modified-timestamps.
what module could be responsible for deleting this row?
I see the same behavior
I did a little snooping and saw the same results.
Rows with "nodeaccess_author" in the "realm" column are untouched... "nodeaccess_rid" rows disappear after an edit.
Thanks for any help.
jackson
seeing the same issue with nodeaccess
I'm seeing what appears to be the same thing. Using nodeaccess, I set permissions for a page. If I edit the page, the permission boxes get un-checked. I tried setting "Give node grants priority" but the problem remained.
Other non-core modules active:
Privatemsg
Autotimezone
LoginTobbaggan (one of the settings here gets rest as well)
Members
Pathauto
Spam
TinyMCE
Troll
Captcha
External Links
I'm new to Drupal, so I expect the issue is probably with me not reading something I should have. Any help is appreciated.
jackson
I think I have solved my
I think I have solved my problem (or atleast found a permanent workaround). I had installed the ForumAccess module a while back. The other day I disabled it (since we plan on using phpBB forums instead of drupal). Now I enabled it again, and my problem does not occur any more.
I have no idea if this is an expected behaviour or not. I certainly would consider that module to be misbehaving.
/Jonas
Didn't help me
That didn't solve my issue. In fact, I complete rebuilt my site (different url, new db and new install of all software and the issue remains.
I also saw this post today http://drupal.org/node/138103. While it makes me feel better that others may have fallen into the same pit, I'm still fairly confident it's my issue or I would see more mails with the same symptoms.
Nodeaccess is everything I need, so I'll keep at it... I just have to remember to update permissions with every change.
jackson
Thank you! I had the same problem, but with OG
Thank you!!! I just googled "access denied 2007 node_access site:drupal.org" and found this post. You described my problem exactly, except the module I had disabled was Organic Groups (OG). I reenabled it and that fixed my problem. I went back as admin and edited and saved the pages involved and they are now accessible again.
Thank you for posting your problem and its solution.
Judy Hallman
I now have this problem too.
I now have this problem too. I need to manually enter a record into the node_access table to make a new page visible. Otherwise, only admins can see the page.
Reading the comments above I believe it is thanks to the Organic Groups module - now deactivated and removed from my system.
Surely there is a simple solution to this problem we are having? It shouldn't be necessary to re-enable modules we don't want activated just to get access permissions to behave.
EDIT: FIXED! I didn't need to re-enable old modules as a far simpler fix worked for me. I visited:
/admin/content/node-settings
...and clicked the rebuild cache button. Problem gone!
Recreate premissions
to fix the issue.
admin/content/node-settings/rebuild