Why is needed to rebuild node access permissions?
Today, in my site, in the following path : admin/content/node-settings , I see the following text:
***
If the site is experiencing problems with permissions to content, you may have to rebuild the permissions cache. Possible causes for permission problems are disabling modules or configuration changes to permissions. Rebuilding will remove all privileges to posts, and replace them with permissions based on the current modules and settings.
Rebuilding may take some time if there is a lot of content or complex permission settings. After rebuilding has completed posts will automatically use the new permissions.
***
I had to rebuild the node access permissions because All display nodes of my site were disorganized. The sticky nodes of the front page were between other nodes, etc ... The appearence of the site changed significatelly.
The problem was fix when I rebuild node access permissions ... but I want to know why happen this?.
Thanks and sorry for my English.
Álvaro
Comments
nobody?
nobody?
=-=
typically it happens when another access.module is enabled, disabled or uninstalled.
Thanks ... but ... I've not
Thanks ...
but ... I've not enabled or disabled a module since months...The last action that I made was changing the numbers of items to display in the frontpage ... only that ...
What's a access.module?
Thanks for all amigo.
Álvaro
=-=
access modules are those listed in the user authentication / access category in the downloads area.
---
I don't see the PATH that u mean ...
I'm using drupal 6.2. In this version I dont see anything that u mean.
Regards.
Álvaro
up!
up!
The download category is
The download category is user access -> authentication and as previously mentioned it is in the downloads area.
http://drupal.org/project/Modules
Ok ... I saw the modules of
Ok ...
I saw the modules of the path that u mean but I dont have installed any of them.
Another explication of the problem that I had?
Thanks amigo,
Álvaro
=-=
nope, and if the node access table is working correctly now, you will have to wait to see if the table has a problem again.
if at ANY time during the life cycle of the site you used any other module that affects the access table and you didn't remove it correctly, or installed one too many modules that affect access then what I've already discussed is more then likely the problem. The only other way to get into which modules may have caused a problem, is to browse your system table and double check every entry to insure you've properly uninstalled any modules and left no extraneous data behind.
The system table will show you all modules installed and set to 1, and those that are uninstalled set to 0. If you compare with your installation you should be able to pick up on any that shoudln't be there any longer.
I've never seen the access table needing repair in any case other then what I've outlined.
good luck!