WordPress.org

Forums

124

[closed] Upgrading from 2.0 to 2.0.1 (95 posts)

  1. pookguy88
    Member
    Posted 9 years ago #

    Are there any specific instructions on how to do this?
    Thanks

  2. spencerp
    Member
    Posted 9 years ago #

    Don't it provide a link to the information on that, right on the Download page?
    http://codex.wordpress.org/Upgrading_WordPress

    I could have sworn it did..

    spencerp

    NOW I gotta re-update mine....Jesus LOL!! O well!!..

  3. pookguy88
    Member
    Posted 9 years ago #

    yeah, but those instructions are for upgrading from 1.5 to 2.0, there's no mention of 2.0.1

  4. AndreSC
    Member
    Posted 9 years ago #

    anybody know what the diferences between 2.0 and 2.0.1 are?

  5. spencerp
    Member
    Posted 9 years ago #

    pookguy88, those instructions are basically the same to a "T" for any upgrading you're going to do.. I followed them when upgrading from 1.5.2 to 2.0 and didn't have any problems.. <knock on wood> Cause now I gotta re-upgrade mine lol..it's always scary to do lol..

    spencerp

  6. Michael Bishop

    Posted 9 years ago #

    I suggest reading the dev blog, it appears 114 bugs were fixed for 2.0.1 http://wordpress.org/development/2006/01/201-release/
    For the record, over 70 files have been changed, so a full upgrade is really the only option.

    Upgrading should follow the same procedure as always.
    Backup your entire site, including your database.
    Delete all wp files EXCEPT config.php and the wp-content folder
    Upload the new files, then, to be safe, run wp-admin/upgrade.php

    http://codex.wordpress.org/Upgrading_WordPress
    http://www.tamba2.org.uk/wordpress/upgrade2two/
    for a more comprehensive upgrading set of instructions, especially if you've been holding off on upgrading from 1.5.x to 2.x

  7. spencerp
    Member
    Posted 9 years ago #

    miklb, thank you! thank you! for your reply! =) Guy's just follow and do what miklb said.. =) =)

    spencerp

  8. pookguy88
    Member
    Posted 9 years ago #

    thanks for the info guys

  9. tanster
    Member
    Posted 9 years ago #

    I just upgraded from 2.0 to 2.0.1. Selected the default theme. When I go to any category archive, like http://www.tanster.com/?cat=4, I see the error message:

    WordPress database error: [You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND comment_approved = '1'' at line 1]
    SELECT COUNT(comment_ID) FROM wp_comments WHERE comment_post_ID = AND comment_approved = '1';

    Monthly archives like http://www.tanster.com/?m=200601 are okay.

    Everything worked fine in 2.0. How can I fix this? Thanks!

  10. Michael Bishop

    Posted 9 years ago #

    have you tried resetting your permalinks?

  11. tanster
    Member
    Posted 9 years ago #

    By reset permalinks, do you mean going to Options > Permalinks, and clicking "Update Permalink Structure"? I tried that and it didn't change anything. (I use the default permalink setting.)

  12. Michael Bishop

    Posted 9 years ago #

    This may be worthy of its own thread. Check any plugins that effect comments.

  13. tanster
    Member
    Posted 9 years ago #

    Actually, I figured out what it was -- the Adhesive plugin doesn't seem to play well with 2.0.1. Once I deactivated it, everything was fine.

    Thanks, miklb, though, for your help! :) Jennie

  14. armadillo
    Member
    Posted 9 years ago #

    > anybody know what the diferences between 2.0 and 2.0.1 are?

    I used WinMerge to identify the differences and delete the unchanged files, leaving only the modified files for uploading. I've posted a list of these at http://www.dillamore.com/wp201changes.html.

  15. mlvernik
    Member
    Posted 9 years ago #

    I tried upgrading 2.0 to 2.1. Deleted all files except the htaccess file, and config file and of course the content folder.

    Uploaded all new files. Ran the upgrade it said to do. Then no posts showed on the site. Nothing in the categories even though it showed articles were posted. The admin shows the articles. Just not the visible part of the site.

  16. Shelby DeNike
    Member
    Posted 9 years ago #

    Worked for me.

  17. scottyg7
    Member
    Posted 9 years ago #

    IMPORTANT NOTE for anyone using the Optimal Title Plugin.

    I had some problems with my blog at http://www.thecrmcoach.com/blog After running the upgrade program, all I got was a blank page!!

    After a few seconds of horor and hoping no one from digg was trying to dig me, I figured it out...

    First I check the error_log file in the root of my blog. That told me there was a problem with optimal_title() in my header file (I have a custom theme).

    Optimal_title is from a plugin which I had disabled. But, because it was disabled, it broke my page.

    I simply took the line out of my header file which let my page work fine. I then reactivated my plugins, put that line back in and presto! It works!

  18. aindian
    Member
    Posted 9 years ago #

    Someone plz help me!!!
    I changed the required files as was posted by armadillo (thanks mate) but now I cant upgrade!!!
    when I run http://www.angry-indian.com/wp-admin/upgrade.php
    it says,
    Fatal error: Cannot redeclare check_admin_referer() (previously declared in /home/aindian/public_html/wp-includes/pluggable-functions.php:228) in /home/aindian/public_html/wp-admin/admin-functions.php on line 966[]

    Luckily, my site is still running...
    Please help ASAP...

  19. icedog
    Member
    Posted 9 years ago #

    same problem as aindian.....

  20. tqn69
    Member
    Posted 9 years ago #

    Here's my problem. Upgraded per Tamba's instructions. The upgrade went smooth as silk.

    Then I edited an old post and hit "Save." Instead of what I normally see, I get a PINK BAR with the post ID on its left-hand side, at the top of a white screen. I checked under Manage and my edits did save.

    I created a new private post and the same thing happened. This also happened on a friend's blog (hosted on a subdomain) that I just upgraded to 2.01.

    What the heck's going on?

  21. tqn69
    Member
    Posted 9 years ago #

    Me again. I can confirm that the PINK BAR posting problem also occurs when I try to publish a new Page.

  22. Xander
    Member
    Posted 9 years ago #

    I had some trouble with saving posts... when I view source on post.php there was a section that looks like this:

    <input name="referredby" type="hidden" id="referredby" value="<div id='error'>
    <p class='wpdberror'><strong>WordPress database error:</strong> [You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near ') ORDER BY post_id, meta_key' at line 1]
    SELECT post_id, meta_key, meta_value FROM wp_postmeta WHERE post_id IN() ORDER BY post_id, meta_key
    </div>redo" />

    I tracked it to:

    url_to_postid($_SERVER['HTTP_REFERER'])

    This code from "edit-form-advanced.php" outputs the error. I'm not sure what it does, so I'm commenting out this part of the conditional statement. Everything seems to work fine now, but what is this functionality for? Is it broken or did I do something daft? :)

  23. Stahn
    Member
    Posted 9 years ago #

    I wanted to cry (not literally) when I saw the error of tanster (I use Adhesive plugin too).

    Thanks for mentioning it! Since the permalinks of my 2.0 installation suddenly stopped working, I was really decided to start again.

    And my permalinks work again now, I'm really glad =)

  24. tanster
    Member
    Posted 9 years ago #

    Stahn, did you receive the same error message as I did when Adhesive is activated?

  25. Antonio
    Member
    Posted 9 years ago #

    2.0.1 does not work with mysql 3.x.x
    one of my blog http://phpbbcn.com lost all the entries :(

    but the other in mysql 4.1 works fine.

  26. spencerp
    Member
    Posted 9 years ago #

    On the side note: I know most do it, but disable ALL the plugins regardless...and yet still "keep the thought" in your mind that some plugins might NOT WORK with a new upgrade.

    Just becareful and if need be, keep certain plugins turned off.. until you get further notice of the "plugin maker". =)

    Also, this upgrading is "scary" and I know how ya'll feel. Believe me...the "blog" is your "lifeline".. to a degree. The comments and replies from everyone, is a tool for others to learn from in a sense. =) So others might not make that same mistake as you did or visa versa!

    spencerp

    <sighs!> And still has to update mine..<worries>..but that is always normal lol..

  27. Fanatyk
    Member
    Posted 9 years ago #

    got problem with polish signs :(
    look at http://www.fanatyk.org :(
    whats wrong? I've done everything step by step with readme :(

  28. tqn69
    Member
    Posted 9 years ago #

    All's well now. My posting problems (where after posting anything I'd see a pink bar across the top of an empty white screen) turned out to be plugin-related. It was caused by an older version of the GEO plugin, version 1.9. Owen must've changed the numbering scheme, because the lastest version that I downloaded from http://www.redalt.com/downloads/ is version 1.0.

    In any event, GEO version 1.0 is compatible with WordPress 2.01.

    So now I can say... nice, bug-fixin' upgrade!

  29. wohnung
    Member
    Posted 9 years ago #

    @Fanatyk: what is exactly incorrect with you polish characters. on my browser, everything seemed to be display ok. I also have a beta for my kontaktanzeige site which uses german symbols and have't had any issues yet. P.S. Please also mention the build version you installed.

  30. torifile
    Member
    Posted 9 years ago #

    I had problems with the Adhesive plugin activated, too. I had just 2 posts listed, with no text in them and filed under "uncategorized". At first, I panicked then I turned off adhesive and all was well. Unfortunately I didn't even get an error message, I just thought my DB had been corrupted. After disabling the plugin, everything works. Even uploading files via ecto. Thumbs up for the update!

124

Topic Closed

This topic has been closed to new replies.

About this Topic