Viewing 12 replies - 16 through 27 (of 27 total)
  • Hi, I attempted to upgrade to 2.3.1 and received these two errors:

    Warning: main(./wp-blog-header.php) [function.main]: failed to open stream: No such file or directory in /home/happybur/public_html/index.php on line 4

    Fatal error: main() [function.require]: Failed opening required ‘./wp-blog-header.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/happybur/public_html/index.php on line 4

    What do I do to resolve/fix?

    Help please. Thank you!

    Update – same errors, now on line 2 instead of line 4

    All better. Used fantastico via blue host. Huh.

    After upgrading a blog from 1.5 to 2.3.1, all pages that were not in wp-admin showed up blank.

    When comparing /index.php with /wordpress/index.php (the former being “old”, as in “already there in 1.5), I found out that in the NEW index.php, there’s a define before the wp-blog-header.php file is included. After adding that to the /index.php file, everything was peachy again:

    define('WP_USE_THEMES', true);

    This makes perfect sense, of course, but since you get NO OUTPUT whatsoever, it’s a bit hard to figure out. Hope this helps someone.

    Be sure your theme is compatible with 2.3.1, that was the problem that my pages remained blank.

    Thread Starter vogelap

    (@vogelap)

    I switched back to the default WP theme and the problem persists.

    You are quite likely getting a PHP error. It is even possible that you have a version of php to old to run 2.3.

    The way I would solve the problem relies on the fact that I have telnet/ssh access to my servers and have access to check the error log generated by PHP.*

    So, I would log in via putty ssh and run this line:
    sudo tail -f /var/log/httpd/error_log

    That’s a fairly standard located file but I can’t tell you if you require the sudo or not or if you even have access to php’s error log. But if that works for you, you will have more information than you did before…

    *Footnote: This also assumes that PHP is configured with log_errors=on. This can be checked by creating a php file calling

    <?php
     phpinfo();
    ?>

    That will tell you the php version and you can search for log_errors

    Thread Starter vogelap

    (@vogelap)

    Thank you for your reply, Brian. I also have telnet/SSH access to my machine, so I think we’re on a good path here. I will attempt the upgrade again shortly and will monitor the PHP log as you suggested.

    For the record, my log_errors is ON, and my PHP version is 5.1.6. I believe that version of PHP is more than sufficient to run WP (as it is currently running 2.2.3).

    Any additional suggestions would be appreciated.

    Thread Starter vogelap

    (@vogelap)

    Brian… Thanks again for your guidance. Your suggestion to use “tail” led me to a permissions error on my /wp-admin/includes directory that was preventing the upgrade. Fixed that and the upgrade went fairly smoothly.

    I′ve been following this thread since I have the exact same problem as Vogelap (as described in her/his first post here).

    But how do I solve it like Brian suggested? He wrote “log in via putty ssh and run this line: sudo tail -f/var/log/httpd/error_log”

    I don′t now what putty ssh is? I have my site at a web hotel, does that matter? If my question seem stupid it′s becaue I don′t understand much of php and databases ??

    I′m very thankful for any help.

    One more possible solution added to the mix:

    My host suggested that there is a small incompatibility in 2.3.x with PHP 5.

    The suggested solution: In the file wp-includes/taxonomy.php in 2.3.3, on line 11, 12 and 13 “(object)” needed to be removed before the array.

    This edit solved the blank page installation issue for me. Hope this helps someone.

    After upgrading a blog from 1.5 to 2.3.1, all pages that were not in wp-admin showed up blank.

    When comparing /index.php with /wordpress/index.php (the former being “old”, as in “already there in 1.5), I found out that in the NEW index.php, there’s a define before the wp-blog-header.php file is included. After adding that to the /index.php file, everything was peachy again:

    define(‘WP_USE_THEMES’, true);

    This makes perfect sense, of course, but since you get NO OUTPUT whatsoever, it’s a bit hard to figure out. Hope this helps someone.
    Posted 2 months ago #
    征途私服

Viewing 12 replies - 16 through 27 (of 27 total)
  • The topic ‘2.3 Upgrade Problem’ is closed to new replies.