Support » Installing WordPress » upgrade problem

  • I’m trying to upgrade from 1.0.1 to 1.0.2. My 1.0.1 blog has been working just fine.
    I downloaded the 1.0.2 package and unzipped it to my local computer. My web site is located at a remote server.
    I went to the readme.html in the 1.0.2 package. Following the directions in readme.html, I did the following.
    1) Made a backup of my data. (Done)
    2) went to sitename/wp-admin/upgrade.php. This resulted in numerous SQL errors. At the bottom of the errors was the message “There’s actually only one step. So if you see this, you’re done. Have fun!”
    Needless to say, my blog was not upgraded to 1.0.2. I verified this by logging into the administration interface and looking at the version number.
    The readme.html instructions are defective for upgrading to 1.0.2 from previous WordPress versions.
    The Wiki is equally vague.
    Should I delete all the WordPress files on my web site (except upgrade.php) and then go to upgrade.php? Should I upload (via FTP) all the new WordPress 1.0.2 files to my server, overwriting the old versions, and only then go to upgrade.php? How do I actually get the new files to my server, and how does that fit in with upgrade.php?
    The 1.0.2 readme.html file says “It is strongly recommended that you use the new index.php for your templates.” Why? I’ve edited my index.html file. It was painstakingly done. Do I have to make a copy of that before I upgrade, and then go about the tedious manual process of putting in all my changes all over again? Is there a shortcut?
    All help is greatly appreciated.

Viewing 10 replies - 1 through 10 (of 10 total)
  • Ack.
    “I’ve edited my index.html file”
    That should have been “I’ve edited my index.php file”

    so u just downloaded the latest file on ur local system?
    u just have to take the backup.
    upload the latest files.
    except for the changed index and css files.
    make sure all the files are uploaded properly.
    run upgrade.
    thats it!

    Assuming you have wordpress 1.0.1 installed in the directory on your server, you have to upload all the files from 1.0.2 to the same directory.
    Then you should point the browser at
    The new index.php might be using new methods/code and that’s why it’s suggested that you change to the new index.php
    Copying over your modifications should be an easy enough task. Easy enough = 0.5 hours.

    @ awh. What you are experiencing is commonly called in these parts the Sushubh effect. It gives the appearance of being totally screwed up but in fact it works perfectly. (Not that Sushubh is anything like that – history does not relate who named the effect or why). The solution is to ignore it, click at the bottom , for the next stage and you really are done. As advertised. Welcome to Word Press 😉

    Dont forget to take a backup before you do anything…
    I dont want to endup getting sued for being the Sushubh in SushubhEffect!
    And well, Craig the nuclearmoose discovered this bug… 🙂

    I don’t think I’ve posted my appreciation yet. WordPress is really cool. At this early point in its life, it’s great already, and the potential exists to really make it something special.
    I got the upgrade done. No major problems. My blog is now on 1.0.2 with no major problem. There is a minor problem I talk about below. Thank you for all the help.
    This might get boring.
    First, a related whine. I really wish the readme.html file in the upgrade package would contain one more sentence. This would be: “After backing up your data and before going to upgrade.php, replace the older WordPress files with the files from the new version.”
    Thank you for the funny SushubhEffect thing. Once I upgraded all the files and then went to upgrade.php, however, there were no errors that came up on the screen.
    Now for the minor problem. According to the release notes for 1.0.2.,
    “Certain characters stripped from comment URIs fixed”
    On the basis of that I thought that 1.0.2 would fix a problem I was having.
    In my old Greymatter blog, there were some comments with “a href” anchor tags (links). These were not displaying properly in WordPress 1.0.1. The links were broken. These links were in the bodies of the comments. Only those links were broken. The other links in comments were fine. For example, the “URI” portion that optionally is linked to the commentor’s name were fine.
    Here is the opening part of one of the broken anchors, as it appears in WordPress “Edit Comment.”
    href=& quot;http://
    IowaAds.htm& quot;
    (spaces and CR’s added)
    As you can see, the quot thing is used instead of a “. This seems to validate okay as XHTML 1.1, but IE, Mozilla, and even Netscape 4 all barf when they try to follow the link.
    With 1.0.2, those broken links in the body of old, imported comments are still broken. I thought that 1.0.2 would just fix them, but I guess it really doesn’t do that.
    I guess the only solution is to go back through all of my old posts, find all of the old links, and change them all by hand. I only have a handful of such posts anyway. The trouble will be finding them. I think I’m going to take a copy of an ASCII SQL dump of my database in a capable text editor, do a search for “& quot;http” (space added) then go to the comment and fix it through the WordPress administrative interface (AKA “Edit Comment.”)
    Once again, thanks for all the help.

    BTW, the link I gave in the example is broken anyway.
    By “barf” I could have also said “append a
    % 22 (space added)
    to the end of the URI followed.”
    Thus, if someone in my old blog linked in the body of a comment to
    and now someone finds that comment, it having been imported into my WordPress archives, and from there sent to the web client as
    “a href=& quot; quot; “
    a click on the link will cause the web client to open the URI: 22
    (space added)
    This on most web sites will result in not the page targeted, but a 404 page.

    I opened up my SQL dump in a good text editor, and started searching for
    Unfortunately, the comments are kept separate in the database from the posts. Thus, it is hard to tell in which post the comment was made. Once I figure out which post the comment was in, I can go and manually edit each comment so those strings are fixed in the proper manner of:
    and so on.
    Time to get tricky. I find a problematic URL in the SQL dump. Then I find some nearby text and copy it to the clipboard. Since I’m using Windows, I open up the Find dialog. I use “containing text.” When I upgraded from Greymatter to WordPress, I happened to keep a local hard drive copy of my entire old Greymatter blog. That has turned out to be a good idea. I use the Windows Find dialog to search the subdirectory where my old Greymatter blog files are located. That gives me a filename that works as a clue. From the filename that I can deduce where the post is in my current WordPress blog. This is possible because I created redirects from my old blog entries to the new. I described that process before.
    I go to the WordPress blog entry with the problematic URL in the comment text, and edit the comment. After repeating this, all the URLs work again.
    Fortunately (or not), I have never had many comments posted to my blog. Thus I don’t have to wade through hundreds of them.If I did, I would look into something automatic.
    It’s kludgy, but it works.

    Hi this wordpress is amazing,
    but can someone tell me how I can upgrade to 1.2
    Because I don’t really get it..

    OK. Nothing to it. In theory. You have two choices. Install over the top. Or start on a clean install and export / import your files. It is however important to mention, that even if you are doing a new install it is necessary to carry out the install proc the run wp-admin/upgrade.php as well . Which ever way you go please back up your data before you start. And if you have an earlier version, make sure you have copies, of your index.php and wp-layout.css. They are both reuseable. If you post a slightly more detailed q, then many folks will help. Welcome to Word Press. (not so much a piece of software as a way of life.)

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘upgrade problem’ is closed to new replies.