'update.php')) Īnd now on the admin/reports/status page you'll see the exact name of the module instead of having to bounce over to the db log (yes, yes. You should run the database update script immediately.', => $module, => base_path(). $requirements = $t('The module (and possibly others) has database schema updates to install.
You should run the database update script immediately.', => base_path(). $requirements = $t('Some modules have database schema updates to install. but instead up at the root level) - should be around line 420 change In /modules/system/system.install (not in sites/all/. +1 Thanks others who are having difficulty with this here's another angle you can take. I did this all in a test environment and have not seen any negative impact of this fix process. Had three different modules that were bad but after repeating this process for each module, the status page is happy. Only one gave me an error where it was trying to create an index that was already created so skipped to the next schema version in line (as found in the modules install file). This found the database updates for the module and ran them. Then updated DB 'system.schema_version' to the found schema number and ran drush updb. install file for the first schema version.
Seeing what module was out of sync, reviewed the modules. watchdog('module update db', $module) // <-ADDED THIS LINE What I did was to temporarily edit core modules/system/system.install and added a watchdog statement before the first requirements line (next). Know this is an old thread but this helped me also and maybe this update will help others.
0 kommentar(er)
