Closed (works as designed)
Project:
Nodeaccess
Version:
5.x-1.2
Component:
Miscellaneous
Priority:
Critical
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
11 Jul 2009 at 04:49 UTC
Updated:
17 Feb 2011 at 22:17 UTC
Jump to comment: Most recent
Comments
Comment #1
danielb commentedsounds like you've done it wrong, use the devel module to debug who has nodeaccess to what, you may find something else going on.
Comment #2
yestuzi commentedIf any Windows error you can try to clean your registry.
the majority of computer problems are related to the registry. When it gets filled with corrupt files and errors,
http://www.make-pc-faster.com/
Comment #3
mkelly commentedI'm seeing this as well, on a Drupal 5.19 installation.
After deactivating the nodeaccess module, anonymous users viewing newly created Page nodes get "Access Denied" errors. Permissions are fine (anonymous has view perm on node content) and there are no other access restrictions in place.
Am going to try the devel module next.
Comment #4
mkelly commentedUnlike the original poster, I was able to remove nodeaccess from my module list properly.
However, newly created nodes are *not* visible by the anonymous user. The anonymous user has the "access content" permission. But according to the devel module:
username view update delete
admin yes yes yes
Anonymous no no no
and no other info is posted by devel beneath this header:
node realm gid view update delete explained
(checked the page source to make sure it wasn't being CSS-styled out of existence. There is just nothing there).
If we re-enable nodeaccess then we can create accessible pages once again.
This is a production site & therefore "most uncool" behavior.
Comment #5
mkelly commentedUpdate:
Rebuilding the drupal node access permissions seems to have done the trick. Something that you might want to mention in the uninstallation of the nodeaccess module.
http://drupal.org/node/122476
Comment #6
Anonymous (not verified) commented