After doing all the mentioned steps in "upgrade.txt" during the upgrade fron D6.19 to D6.20 at the final step which is running "update.php" I'm getting only a white screen. I can not get access to any part of my web site. I have searched Drupal.org and some have been reported this issue but they got this because of deleting the garland theme. But in my site garland is in it's place and in variable table i can see this theme have been set an default.
theme_default s:7:"garland";
when running the update.php i'm getting the following erros in error console of firefox:

Warning: Unknown property 'pading'.  Declaration dropped.
Source File: http://www.iclub.ir/update.php?op=info
Line: 290
Warning: Unknown property 'pading'.  Declaration dropped.
Source File: http://www.iclub.ir/update.php?op=info
Line: 295
Warning: Unknown property 'background-background'.  Declaration dropped.
Source File: http://www.iclub.ir/update.php?op=info
Line: 645

Is there any solution to this issue?
(this is my live blog)

Comments

lameei’s picture

lameei CreditAttribution: lameei commented
Component: update system » ajax system

Nothing yet?

rfay’s picture

rfay
Primary language English
Location Palisade, CO, USA
CreditAttribution: rfay commented
Component: ajax system » database update system
Status: Active » Postponed (maintainer needs more info)

Your explanations may not have to do with core at all - they may have to do with a contributed module.

To actually solve this, you'll have to copy this site to a sandbox and do this over and over until you can figure it out. Probably you'll need to disable several modules, try again, see if it happens, re-enable some of those modules, etc. This approach may get you somewhere.

The divide-and-conquer ideas at http://randyfay.com/node/42 may help you (as well as the general ideas at http://randyfay.com/debugging).

In general, you'll never get this report solved with the amount of information you've provided here. All you've basically said is "I have a white screen of death when running update.php" and that can have so many causes that nobody can help you. You may want to read about the White Screen of Death and the related troubleshooting portions of the handbook.

lameei’s picture

lameei CreditAttribution: lameei commented
Component: database update system » ajax system
Status: Postponed (maintainer needs more info) » Active

@rfay thanks for the reply i will do the same you mentioned with the links. actually i restored a recent backup and now the blog is up and running.
Will reply here if i got some new clues.

rfay’s picture

rfay
Primary language English
Location Palisade, CO, USA
CreditAttribution: rfay commented
Component: ajax system » database update system
Status: Active » Postponed (maintainer needs more info)
verta’s picture

verta CreditAttribution: verta commented
Title: Running update.php fails with white screen (upggrade process from D 6.19 to D6.20) » Running update.php fails with white screen (upgrade process from 6.19 to 6.20)

update title for search engine to locate by "upgrade"

lameei’s picture

lameei CreditAttribution: lameei commented

I did some test here is the report:
After dealing with database and codes i got no positive results so i decided to download all the needed data (blog posts, comments, statistics, ...) from the live DB and create a local copy of the online blog. After creating the blog and importing the downloaded data into the new database i got it working on my localhost. then i purged all the online files and uploaded the site to the host. unfortunately the issue was there preventing me to get my hands on any link starting with admin. But this time i can go to the update.php and update the DB. but no access to admin pages on the host (the white screen shows off). I'm pretty sure that the problem is not cause of the php memory limits as i have more complicates sites on the host with the same specs.
Is it good idea to install drupal from scratch on line and then importing the database tables?

lameei’s picture

lameei CreditAttribution: lameei commented

With using Dtools I was getting

hook_exit wasn't executed properly at admin, possible unexpected exit()/die() Backtrace: hook_exit wasn't executed properly at

in admin page. but now i don't get any errors and the screen in white again. and at the front page using dtools i'm getting

NOTICE: Script execution completed with error: A session had already been started - ignoring session_start()

but the page is loading correctly.
I've searched the above mentioned error and there was not q working solution for me.
PS: The problem is not because of modules, I have renamed the modules folder, The issue remains the same.

lameei’s picture

lameei CreditAttribution: lameei commented
Status: Postponed (maintainer needs more info) » Postponed

I have installed a fresh drupal online and getting the same error. I think this should not have any thing with drupal. reported to the host.

lameei’s picture

lameei CreditAttribution: lameei commented
Component: database update system » update.module
Status: Postponed » Needs review

This is the response from the host:

1. The Update module tries to connect to all web sites listed as update locations for your installed modules and the Drupal installation itself.
2. It is common that one or more of those web sites are not accessible at that point (or are replying too slow). Most commonly it is an issue with third party scripts/modules.
3. The Update modules tries to retrieve the information and since it does not succeed in more than 10 seconds - the scripts times out - a blank page is displayed.

This is why the automatic update check module should be disabled in order for the administrative area to work correctly.

I confirm that with disabling the update modules everything is working right. But should it be this way? I have other websites on the same hosting Co. which is working normally with auto-update enabled.

cweagans’s picture

cweagans
He/Him
Primary language English
Location Boise, ID, USA
CreditAttribution: cweagans commented
Priority: Critical » Normal

Support requests are never critical or major.

Status: Needs review » Closed (outdated)

Automatically closed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.