I am trying to upgrade my site from Drupal 5.7 to Drupal 6.4. I disabled all contributed modules and themes, dropped back to a core theme, deleted all old Drupal 5.7 files, and uploaded the new Drupal 6.4 files. I then copied sites/default/settings.default.php to sites/default/settings.php, edited it so it had the correct info, and set it to be writable by the web server.

Went to run update.php, and I get redirected to update.php?op=info with a white screen. No error message.

I upped the memory limit in my php.ini file to 90M. Same thing.

Followed the suggestions at http://drupal.org/node/158043, putting the suggested lines into both index.php and update.php. Still no error messages on screen or in any of my log files.

Tried re-downloading and re-uploading Drupal 6.4. No change.

My host is DreamHost, and they are running Apache 2/PHP 5/MySQL 5. Trying to access site in Firefox 3.0.1 on Ubuntu Linux 8.04. Have tried clearing cache and cookies.

Any ideas on how to get the Drupal update system to work?

Comments

dan.thompson’s picture

dan.thompson commented

Well, I've even tried removing my .htaccess file in case there was something in it that was preventing update.php from running.

Same problem.

Going to just wipe everything and start over. Its too bad Drupal's update.php doesn't work better. Other than that its a great system.

gpk’s picture

gpk commented

>Any ideas on how to get the Drupal update system to work?
It's always worked fine for me.

I suggest you talk to your host. WSOD usually indicates a PHP error, which should be logged somewhere. Until you manage to find an error message somewhere there's very little that anyone can suggest ...!!!

Possibly you might find some messages (serialized) inside your session data in the {sessions} table.

ainigma32’s picture

ainigma32 commented
Status: Active » Postponed (maintainer needs more info)

@dan.thompson: did you ever find out what the problem was?

- Arie

ainigma32’s picture

ainigma32 commented
Status: Postponed (maintainer needs more info) » Fixed

Looks like dan.thompson won't be posting any feedback so I'm setting this to fixed.

Feel free to reopen if you think that is wrong.

- Arie

amygdala’s picture

amygdala commented
Status: Fixed » Active

i had the same problem, and i couldn't do much because i, too, have dreamhost, and i was dependent on them for error logs...

finally, after switching the installation folder back to drupa. 5.14, i discovered that not all of my modules had been disabled: only those that had dependencies; i really should have gone back to do a second round of disabling modules, but could not the update script check if any non-core modules were enabled and warn me? i'm sure others are making this mistake and wasting time wondering what went wrong...

ainigma32’s picture

ainigma32 commented
Status: Active » Fixed

@amygdala: Thanks for your input. I think your idea of some pre-update check is pretty good and would make the update process more "safe"

Could you open a separate issue and mark it as a feature request?

- Arie

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.