A site I'm working on is not allowing authenticated users to view nodes unless they have "administer nodes" access. I'm thinking this might be a module but have not been able to track down which module might be causing this. Anyone here have any ideas?

thanks

Comments

mblazke’s picture

Hi,
check the "Published" attribute on your nodes - AFAIK only published_nodes are visible per "access content" access right, on the other hand "administer nodes" grants the user to view nodes no-matter of published/unpublished status.
Have a nice day

jkamin’s picture

But could be even larger.

It looks like if a user doesn't have "administer nodes" access they don't see any new content or updates to site - including new nodes, new blocks, new views or even a search box that we enabled.

I know I've done something funny because users without "administer nodes" access can see content that was created weeks ago - but I can't for the life of me figure out what I've done to stagnate the site for all but "administer nodes" roles.

Any clues will be most appreciated. Thanks!

Julia

PS. Yeah, all nodes have the "published" default, so that's not the issue.

mblazke’s picture

(as for Published/Unpublished attribute - that was my own experience... ;-)

...because users without "administer nodes" access can see content that was created weeks ago

1. Isn't it your cache? See http://your_site/admin/settings/performance - the little A larger minimum cache lifetime offers better performance, but users will not see new content for a longer period of time there.
2. Aren't your access info lost? Enabling/disabling some modules may overwrite your previous node access rules (e.g. OrganicGroups)