Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I am having a requiement problem after updating from 7.8 to 7.12. Everytime I run update.php, it presents me a screen with something like this:
Node Access Permissions Disabled
If the site is experiencing problems with permissions to content, you may have to rebuild the permissions cache. Rebuilding will remove all privileges to content 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, content will automatically use the new permissions. Rebuild permissions
OK Superfish library Installed
OK Web server Apache/2.2.17 (Unix) PHP/5.3.6 JRun/4.0
OK PHP 5.3.6
OK PHP register globals Disabled
OK PHP extensions Enabled
OK Database support Enabled
OK PHP memory limit 128M
OK File system Writable (public download method)
Warning Unicode library Standard PHP
Operations on Unicode strings are emulated on a best-effort basis. Install the PHP mbstring extension for improved Unicode support.
Check the error messages and try again. .
Do anybody know what this is and what I should do with it?
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | modules.png | 10.96 KB | ouyang1512 |
Comments
Comment #1
xjmI'd suggest disabling contributed modules to see which might be causing the problem, and/or doing the contributed module upgrades one at a time before updating core.
Comment #2
ouyang1512 CreditAttribution: ouyang1512 commentedFirst, thanks for your suggestions. But is it feasible to disable and then enable all contributed modules just for checking this, given that I have about 35 contributed modules installed? Or is this a contributed module problem? Is there any other way to fix this or find out what the real problem is?
Comment #3
Ranko CreditAttribution: Ranko commentedBlind stab here, but are you using some access control module? If so I'd definitely try rebuilding the permissions (standard disclaimer: backup, test site first, etc.).
Comment #4
ouyang1512 CreditAttribution: ouyang1512 commentedI have actually rebuilt the permissions twice, but the message still does not go away. When you say "access control module", can you please give me an example? At the same time, I am attaching a list of modules I installed, can you help tell which modules might cause this issue? Thanks in advance!
Comment #5
Ranko CreditAttribution: Ranko commentedI was thinking something like access control list, taxonomy access, taxonomy access light.
From what I know, none of these should be causing it. Except maybe CiviCRM. But the best way to check is what xjm suggested, start disabling the contributed modules.
Comment #6
ouyang1512 CreditAttribution: ouyang1512 commentedFor some reason, I am still getting the same problem even after I disabled all civicrm components. But I am able to proceed with the update page when I click the "try again" link. Any other ideas on this issue? Thanks!
Comment #7
dwwI know it's confusing, but "update.module" is for the part of core (added in 6.x) that checks for available updates to your modules and themes (now called the "Update manager" since it can also install/update your code). You're talking about update.php, which is the "database update system" component...
Sadly, I don't have any advice to offer you, but I maintain the update.module in core, so I'm trying to tirage "my" issue queue...