Support » Installing WordPress » 2.0.2 Is out

Viewing 15 replies - 16 through 30 (of 75 total)
  • i put it on my local machine this AM; all good.

    Is there a list of the actual security problem with earlier versions? I dont want to upgrade unless its actually needed!

    And for the inevitable “Can we have a patch?”
    http://somethingunpredictable.com/tmp/201-202.diff

    And for some more detailed patching instructions:

    WordPress 2.0.2 released – Security update

    Upgrade went smoothly but now the page won’t stop loading in Safari (same as this page), I get the following in Safari’s activity window:

    http://www.google-analytics.com/_…Fblog%2F%7Cutmcmd%3Dreferral%3%2B

    and I’m wondering what this is.

    Thank you.

    You’ve got a google analytics plugin problem.

    anyone have an idea why i would get this error:

    Warning: main(/var/www/html/blog/wp-includes/wp-db.php): failed to open stream: No such file or directory in /var/www/html/blog/wp-settings.php on line 73

    Fatal error: main(): Failed opening required ‘/var/www/html/blog/wp-includes/wp-db.php’ (include_path=’.:/php/includes:/usr/share/php’) in /var/www/html/blog/wp-settings.php on line 73

    Make sure all the files are uploaded into the blog/wp-includes/ directory, especially this file: wp-db.php

    And make sure they are all uploaded into the other directories and the root like “supposed” to be.. =)

    That error you recieved is basically telling you what is not there and or where the file is supposed to be at. =)

    Warning: main(/var/www/html/blog/wp-includes/wp-db.php): failed to open stream: No such file or directory in /var/www/html/blog/wp-settings.php on line 73

    I hope this is right…it should be the reason for the error lol.. =)

    spencerp

    Due to another problem, I installed 2.0.1 and, then, decided to upgrade to 2.0.2. (In the end, it turned out that I did not need to install 2.0.1 but that’s another story.)

    I read the upgrade instructions:

    http://codex.wordpress.org/Upgrading_WordPress

    and noted that it said not to use upgrade.php. Ok, so I went further down the codex and found the following:

    1. Delete /wp-admin/ folder.
    2. Delete /wp-includes/ folder. Note: You must backup /wp-includes/languages/ directory if exists.
    3. Delete all the wordpress files in the root directory where the root index.php file is found. DO NOT DELETE wp-config.php.
    4. Download and extract the new version.
    5. Upload it to the appropriate folders such as /wp-admin/ and /wp-includes/.
    6. Upload all the files in the root directory.
    7. If existed, restore /wp-includes/languages/ directory

    Is it just me or are #5 and #6 a bit vague? In the end, I simply kept my wp-config.php file and replaced everything else in the directory with the new 2.0.2 files. It seems to have worked out fine.

    Ran the upgrade from 2.0.1 to 2.0.2 this morning, went smooth as silk!
    Keep up the great work!

    I encountered the same problem as shakemusic. Since the initial installation of WP was more luck than knowledge (I have the wordpress files in both the root and my /weblog folder and deleting any single file completely screws everything up), that scared the **** out of me! :-0 So I put back the old files and I’ll try again later.

    Is there a list of the actual security problem with earlier versions? I dont want to upgrade unless its actually needed!

    There is no formal list, but let me say that the upgrade is absolutely necessary, the vulnerabilities are not crackhead zero-chance holes, they could easily be used to bring your blog to its knees.

    I followed the intructions to the letter, yet at the bottom of my dashboard page I still see “2.0.1 — 0.10 seconds” and when I click view source I still see <link rel=”stylesheet” href=”http://www.focusedandfree.com/wordpress/wp-admin/wp-admin.css?version=2.0.1″

    Does that mean the upgrade didn’t take or ???

    I did the upgrade from 2.0.1 to 2.0.2 and I see a 2.0.2 – 4.95 seconds.

    I have to say, for someone who isn’t very technical at all when it comes to this stuff, the upgrade was very easy! See? I knew there was a reason why I dumped movabletype and got wordpress!

    Upgraded today 2.0.1 -> 2.0.2. Followed the 7-point list in the Codex. Dead easy, took less than 5 minutes. And it works 🙂

Viewing 15 replies - 16 through 30 (of 75 total)
  • The topic ‘2.0.2 Is out’ is closed to new replies.