Posted 5 years ago #
I currently have 2.1.3 and am trying to upgrade to latest. When I follow the directions, I end up with a blank presentation for my site. The admin tool shows all content, but the main page for users is empty.
Do I need to apply each release from 2.1.3 to current or can I jump straight to the latest (2.3)?
Please help.
Yes you are supposed to be able to go directly from 2.1.3 to 2.3.
I'd check to make sure you got ALL your WordPress files uploaded successfully.
You might consider redoing Steps 7 and 8 as listed in Upgrading_WordPress_Extended.
Posted 5 years ago #
jsolutions, a blank page usually means there is a PHP error. Check your logs.
Is your theme compatible with WordPress 2.3? Have you disabled all of your plugins to see if that is the problem?
http://codex.wordpress.org/Themes/Theme_Compatibility/2.3
http://codex.wordpress.org/Plugins/Plugin_Compatibility/2.3
Posted 5 years ago #
Thanks for the replies.
I changed to the classic theme before upgrading. This should have resolved that issue (I think).
I disabled and even deleted all extra plugins (there was only 1) before the upgrade.
What error logs are we referring to? The webserver logs?
Posted 5 years ago #
I checked the webserver logs -- there are no errors. I did get a database error on upgrade related to options not having a default value.
Note that the main page of my website shows blank and when I do a view source, I get the following.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=windows-1252"></HEAD>
<BODY></BODY>
<META content=WBVNTMRYKT name=SKYPE_FRAMEID></HTML>
Posted 5 years ago #
Today is a day when I want to change careers.
The index.php file at the main level has the following line:
require('./wp-blog-header.php');
Based on some inserted text, I discerned that the wp-blog-header.php file was not being found. So, on a whim, I took out the "./" and the site started working again.
My strong feeling is that this is an issue with the environment in which wordpress is installed. Does anyone else agree?
One thing to note, is that we're dealing with a Windows web server running IIS 6.
In any event, this issue is closed. If someone can definitively tell me how to fix this issue (so that the provided path to the file will work), I will be indebted to you. Otherwise, this thread is ended.
Posted 5 years ago #
jsolutions, that is very strange! Thank you for documenting it here.
This topic has been closed to new replies.
