The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Server: Shared hosting on an Apache web server with PHP 5.2.6, MySQL 5.0.41 and Drupal 6.4.
Installed modules:
* Views 6.x-2.0-rc4
* Poormanscron 6.x-1.0
* Token 6.x-1.11
* Pathauto 6.x-2.x-dev (2008-sep-13)
* Lightbox2 6.x-1.8
* Google Analytics 6.x-2.x-dev (2008-okt-01)
I have been using the latest release candidates without problems and living happily with them, yesterday however I updated CCK 6.x-2.0-rc7 to 6.x-2.0-rc8 . Or rather, I tried. I took a backup which was moved out from the directory, replaced the module in sites/all/modules directory with the new version and went on to use update.php with the automatically selected choices, which tried to do five updates.
The result (see attachment) was an error page asking me to enable CCK in the admin/build/modules before the database updates could be performed, which was odd since it should have been enabled, after all I have successfully been using it for a few weeks now.
But I went to the modules admin page to see what is wrong and I am greeted by a blank white page. "This is not looking good..." was my thought, and that being true the only thing I am able to access at all without being fed a blank page is update.php, everything else except the admin page is unreachable.
At this point I decided to roll back to previous reason, since update.php reported that it did not run any databas updates I replaced the newer version (RC8) with the older (RC7) and tried to access my site. Still blank. Running cron? Still blank. Cleaning cache? Still blank. Running update.php? Still blank.
And now I am stuck with an admin interface and no ideas what to do next.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | updates.png | 39.96 KB | NiklasBr |
| #6 | select-modules-from-db.png | 124.03 KB | NiklasBr |
| #6 | select-modules-only-core.png | 96.57 KB | NiklasBr |
| cck-rc8-update-error.png | 43.68 KB | NiklasBr |
Comments
Comment #1
karens commentedSince you have a backup, go back to your backup database, use CCK rc9 (which will be issued later today), and try again. Before running the update, check your modules page to see what modules are enabled, just so we can be sure. Also, just in case we have a theme issue here, be sure to set your admin theme to a core theme like Garland.
Then try the update again. You will probably still get messages to re-run the update and you may have to run it several times before everything will update and the message will disappear.
Comment #2
NiklasBr commentedStarted with RC7, installed RC9 and ran
update.php, which only gave one error this time, but also tried to only update one table, not the five that RC8 tried to update. The error is the same kind that I attached above: I need to enable content.module to be able to run the update.My admin theme is Garland and the
admin/build/modulesis completely blank. Not a byte sent to the web browser. However,admin/build/modules/uninstallis possible to reach.Comment #3
karens commentedWhat theme are you using for an admin theme? Try making your admin theme Garland and see what affect that has on being able to get to the modules page. [Edit] You did that already, sorry I missed reading that.
Turn error messages on in your PHP settings, that 'blank' page will have an error message if you do.
Comment #4
NiklasBr commentedadmin/settings/error-reportingis set to write to screen and log. No custom 403/404 pages.admin/settings/logging/dblogis set to save the last 1000 log posts.admin/reports/dblogreports nothing on what happens when I runupdate.php.admin/reports/statusis all greens.Though I realise that I actually managed to find one thing with RC9 that I could not do with RC8: access some pages on the site. When I tried RC8 e.g. the page
www.mysite.cm/forumwould be blank, with RC9 this is not the case. Now the only blank page are those which show content from CCK fields plus theadmin/build/modulespage.Edit: Tried to see if
admin/settings/error-reportingwas working as it should, removing the Pathauto module from its directory triggered error messages on the screen and in the log.Comment #5
karens commentedWhat non-core CCK modules do you have installed? If you can't get to the modules page, you can turn them off by setting the status to '0' in the system table. Try turning off all non-core CCK modules to see what happens.
Comment #6
NiklasBr commentedQuery:
SELECT filename, name, type, status, schema_version FROM `sjoskogen_system` where status=1See attachment 1 for result. When I only have these (second attachment) modules installed I still get the blank pages.
Comment #7
karens commentedTurn off lightbox, poormanscron, google analytics. Clear all your caches.
Comment #8
karens commentedDo you have non-core CCK modules in the modules folder, even if disabled?
Comment #9
NiklasBr commentedI did turn them off in the second attachment, however that had no effect. Cleaning cache and running cron had no effect.
Comment #10
karens commentedI'm out of ideas and I certainly can't replicate this.
Try a fresh install in the same environment where you're having trouble and see if things work that way.
Comment #11
NiklasBr commentedKarenS, a huge thank you for taking your time and energy to help me.
Now I feel really stupid because I cold just have run a SQL query to
{system}to setstatus = 1for the cck content.module. I did so recently and then usedupdate.phpand now everything is working as it ought to.I have no clue whatsoever about why it happened like it did though.
Comment #12
karens commentedI'm going to assume that you just had some kind of hiccup, rather than that this is a bug in CCK. Since no one else has reported this and you're fixed, I'm going to mark this fixed.
Comment #13
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.