Posted by adshill on February 12, 2008 at 1:47pm
17 followers
Jump to:
| Project: | Drupal core |
| Version: | 6.2 |
| Component: | ajax system |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
After an update from RC2 to RC4 I'm trying to run the update.php script but it is just bringing up a blank screen with none of the wizard that I previously used to update on RC2... I'm being told within my status report to update my database but this isn't possible due to the above.
I'm not sure if this is something obvious but I don't see it at the moment.
Tested on Firefox 2.0.0.12 and Safari 3.0.4 on Mac OSX Leopard 10.5.1
Comments
#1
Could you please try to re-download an RC2 , install it in another database and then try RC4? Ie. is this reproducible?
#2
Also please confirm your php memory limit.
#3
do you get a white screen after clicking on the update button in
update.php?op=selection, or is it before that stage that you get a white screen? when you go toupdate.php, are you redirected toupdate.php?op=info?#4
Its when I go to the myurl.com/update.php address - ie. before any of the update screens even kick in.
Memory limit is at 16Mb.
I'll try and recreate with fresh installs as soon as I can, although all I had done on my current site is add some content and the image module. In addition I attempted the update a second time with exactly the same problem.
Will feedback after I test on a fresh install but likely to be a day or so...
#5
Do you only have the image module enabled? Try to disable all the modules and see if you can reproduce. Also it'd great to check your php error logs.
#6
for me disabling the devel module temporarily helped...
#7
same problem here. Devel is not installed. memory limit is set to 64MB. What confuses me is: I'm going to update.php and there's no loading time. The white screen jus pops up.
And this used to be an 5.7 page. I upgraded it. So far this is the only problem i got.
#8
OMG... pretty stupid. I somehow still had the old 5.7 update.php file in my file system... argh.
#9
Moving this to a generic support request for now.
#10
removing all sites/all/modules directory from server worked for me, i have to update all of them anyway
#11
Going to assume that the test using a fresh install worked.
Feel free to reopen if that is incorrect.
- Arie
#12
Automatically closed -- issue fixed for two weeks with no activity.
#13
php errors showed views to be the culprit - moved that and was fine...
#14
"php errors showed views to be the culprit - moved that and was fine..."
Where did you move it please?
thanks
#15
UPDATE What I did below seemed to have disabled many modules, so I'd be careful and make sure you know which modules you have enabled before you do this!
Turns out that the white screen was coming from bad code in a single module. The solution that worked finally was to move one module at a time outside of drupal and run update.php again. When it did work, then I had isolated the module.
The next step was determine the bad code in the module, again by making small changes, rerunning update.php until it worked.
Original Text
I moved sites/all/modules out of the drupal installation and ran update.php; the white screen was no more; it fixed the problem. Then I put the modules folder back in it's correct place and ran update.php again without a problem. You should be able to achieve the same thing by renaming the modules folder to something else, say "#modules" temporarily; thought I didn't try that.
Notes:
* I did not have any php errors in the beginning and,
* I was going from 6.14 to 6.15
#16
Aklump...you saved my bacon on this. I had upgraded several other sites to 6.15 without issue, but today I had horrendous and hobbling issues and errors (it was an Acquia install). I renamed the modules/acquia folder...did the update, and (finally) VOILA...thanks
Mark
#17
I had the same problem as you. When i did the upgrade i didn't want to change my themes so i just thought i wouldn't drag any themes over. but apparently update.php needs the new themes to run that page..
#18
Moin moin,
if someone still got this Problem, maybe you'll have the same problem I do.
I have a very basic setup but have "renamed the garland theme" for some reasons i can't remember anymore :)
/update.php?op=info was showing only a blank screen. After renaming the folder of the garland theme back to its original name,
my problem was fixed.
Hope it might help someone.
Regards,
yours-truly.de
#19
I had the same issue that was related to the Garland theme. Deleting and replacing the entire Garland theme folder with the latest version solved my update.php problem. I don't recall ever renaming that theme and I'm fairly certain that it was the latest version but a fresh new version of it did the trick.
#20
I experienced this problem on a D6 site after I had downloaded and installed the latest version of Views (6.x-2.14) and found that the problem was caused by views_clone_display still be installed. Views 6.x-2.14 now provides the clone display functionality and there was a namespace collison with this now unneeded module. I removed the views_clone_display directory and was able to run update.php fine.
#21
Thanks DarrellDuane your tip has also helped me solve my problem!