WordPress.org

Support

Support » Installation » [Resolved] WordPress 2.7 Blank Page Problem (Upgrade & Fresh Install)

[Resolved] WordPress 2.7 Blank Page Problem (Upgrade & Fresh Install)

  • For the last couple of days I’ve been trying to get 2.7 working. But seen I’m posting here I’ve had no success. I tried installing it fresh on my server and by upgrading 2.6.2.

    I’ve tried:
    *Installing fresh from source to FTP server (in the root of httpdocs)
    *Installing by upgrading from existing 2.6.2 version provided by auto installation (4PSA Integrator) from my hosting provider.
    *Installing by upgrading from existing 2.6.1 version by using the InstantUpdate and Automatic Updater Plugins. InstantUpdate works perfectly, but leaves me with the blank page problem. Automatic Updater for some reason cannot read my files (despite their permissions being 755 and 777)

    I’ve also on the above the following
    *Using different FTP programs (Transmit, Cyberduck Filezilla)
    *Using ASCII, Binary and Auto upload function
    *Disabling PHP safe mode (my host had turned it on for some reason)
    *Giving all my wp-files (recursively) 777 and 755 permissions (despite it being stupid, i know)
    *Uploading content to overwrite old files, twice. (worked for others)
    *Deleting old files before uploading
    *Googled extensively and tried all other solutions offered on WP forums.
    *Shouting at it…

    Anybody an idea about what i should try next?

    Thanks in advance

Viewing 15 replies - 1 through 15 (of 40 total)
  • I had this exact same problem using Firefox 3. When I tried looking at the same page that was blank with Firefox 3, using IE 7, it works. There’s some minor issues even with IE 7 but at least I can look at my website. Hope that helps.

    I’m on mac and tried both Firefox (3.0) and Safari 3.2.1 but both fail to load the page. With Firefox displaying a blank page for everything, and Safari displaying a connection error.

    I have the same problem. After uploading the files for 2.7, I tried calling wordpress/wp-admin/install.php — this gave me a blank page (in FF, IE, Safari).

    Adding echo "test"; to install.php will output ‘test’ to the page when placed before line 19: require_once('../wp-load.php'); after that it fails.

    Might this be due to the restrictions on include/require that came with PHP5?

    My previous assumption about the restrictions on include/require seems to be correct.
    When I try to include/require a file outside the current directory the script fails and dies quietly. When I copy the same file to be in the same directory.. it works!

    So this seems to be a WordPress+PHP5 issue.. can anyone confirm this?

    I think I might be able to confirm what you’re talking about. Just for kicks, add the code:

    echo ABSPATH;

    to see if WP and/or PHP is getting the correct values for script location.

    My problem is that while my blog works fine, I cannot get into the administration interface, and I attempted to change a few require_once to just plain ol’ require and got into the admin interface for a little while. Now, a blank white screen is all I see on the admin interface.

    My blog is working okay, though.

    While installing trough FTP upload and refreshing the page several times I got snippets of the new interface, but after the upload is done it it goes completely blank…

    Seems to me some code is making WP2.7 go blank with PHP5.

    I found a way which worked for me. Go went to “Design” menu and clicked in the list on the actual theme and saved the “new” configuration. Then everything worked normally.

    Moderator kmessinger

    @kmessinger

    A blank page means a php problem and sometimes, depending on the browsers, you may not see the error message. So first always test in another browser.

    Certificateno
    Check your config.php for errors – that is probably the communication error.

    I know this as on my install I white paged in IE7 but in FF3, there was the message about error connecting to db. Fixed a typo in the config.php file and now all is well.

    I think there might be a problem defining ABSPATH when using php v5.2.8.

    in root/wp-admin/admin.php, I changed some code at the top to tell me if ABSPATH was not being defined.

    if ( defined('ABSPATH') ) {
    	require_once(ABSPATH . 'wp-load.php');
    }
    else
    	{ echo 'Cannot acquire information from ABSPATH variable to load wp-load.php.';
    	require_once('../wp-load.php');
    }

    And lo and behold, the information in ABSPATH isn’t making it to admin.php.

    In addition, because the variable ABSPATH isn’t being defined in root/wp-admin/admin.php, it makes sense that the errors are compounding because root/wp-admin/admin.php relies on ABSPATH to call a very important file that loads the dashboard from root/wp-admin/includes/admin.php.

    <strong>require_once(ABSPATH . 'wp-admin/includes/admin.php');</strong>

    In other words, if ABSPATH is NOT being defined when loading /wp-admin/admin.php, then how can it be expected to be defined when calling /wp-admin/includes/admin.php ?

    Nightblade – Digg50 here – I’ve been following your posts around because you seem to be onto an answer, but I tried changing that code you have there at the top of /admin.php but I didn’t see any change as yet.

    You have this string;
    require_once(ABSPATH . ‘wp-admin/includes/admin.php’);
    but where did you put it?

    Niteblade, thank you for your confirmation..
    but things just seems to be getting more and more strange:

    \\ inside install.php
    
    \\ filename relative to current file
    $wpload = dirname(dirname(__FILE__)) . "/wp-load.php";
    \\ check if file exists
    if(is_file($wpload)){
    	echo "Yes, ". $wpload ." is a file!";
    }else{
    	echo "No, ". $wpload ." is not a file!";
    }
    
    \\ output: No, Server:/sites/www.mysite.com/test/wordpress/wp-load.php is not a file!

    Both absolute and relative paths don’t seem to work. When PHP doesn’t see the file.. how can it be included/required? Hmm..

    I’m giving up and going to stick with 2.6.5 for a while. Maybe the next version of wordpress will work properly for me and the others.

    I’ve tried modifying my config.php with all possibilities described here and on Codex but nothing seems to work. Even static pages like install.php don’t want to show up anymore from time to time.

    Quick and dirty this is my config file. Database and password are working for me, but obscured here. Same goes for the Secret keys.

    <?php
    define(‘DB_NAME’, ‘my database name’);
    define(‘DB_USER’, ‘my user name’);
    define(‘DB_PASSWORD’, ‘my password’);
    define(‘DB_HOST’, ‘localhost’);
    define(‘DB_CHARSET’, ‘utf8’);
    define(‘DB_COLLATE’, ”);
    define(‘AUTH_KEY’, ‘Key #1’);
    define(‘SECURE_AUTH_KEY’, ‘Key #2’);
    define(‘LOGGED_IN_KEY’, ‘Key #3’);
    define(‘NONCE_KEY’, ‘Key #4’);
    $table_prefix = ‘wp_’;
    define (‘WPLANG’, ”);
    if ( !defined(‘ABSPATH’) )
    define(‘ABSPATH’, dirname(__FILE__) . ‘/’);
    require_once(ABSPATH . ‘wp-settings.php’);
    ?>

    Did you try my idea? Change to an other theme, save the configuration. Then go again the the design menu and change back to your theme you had before.

    You may get a hint of the error by seeing the source of the page
    View > Page Source

    Sometimes the files which you have downloaded may be corrupt. Try once again after downloading a fresh copy.

Viewing 15 replies - 1 through 15 (of 40 total)
  • The topic ‘[Resolved] WordPress 2.7 Blank Page Problem (Upgrade & Fresh Install)’ is closed to new replies.