WordPress.org

Ready to get started?Download WordPress

Forums

124

[closed] Upgrading to WP 2.0 (103 posts)

  1. shep
    Member
    Posted 8 years ago #

    Information on Upgrading.

    Backing up your database is <u>ESSENTIAL</u>

    A guide on Codex can be found here:
    http://codex.wordpress.org/Upgrading_WordPress

    A guide can also be found here:
    http://www.tamba2.org.uk/wordpress/upgrade2two/

    The guides may differ slightly but both are safe to use. Please take your time and follow them - and if you are unsure, post here first.

    Changelog
    There have been a huge number of changes (500 +) in the core. Studying Trac will show you all the changes if you are keen on reading that. There is not and will not be a changelog here. It is highly recommended that you fully replace the core files.

    New in 2.0
    Have a read:
    http://asymptomatic.net/2005/11/29/2135/whats-new-in-wordpress-20/

    Multi-user blogs
    There have been significant changes to the user levels. If you have different users, you must satisfy yourself how this will affect your blog. If you run any sort of plugin that restricts what different users see or can do depending on their level you must be confident about the upgrade. Check everything - do not come back here complaining about user levels if you have not checked and made absolutely sure you know exactly what will happen. The place you need to check is http://codex.wordpress.org/Roles_and_Capabilities

    Plugins I
    This page has details: http://codex.wordpress.org/User:Matt/2.0_Plugin_Compatibility
    Check FIRST. Please don't upgrade and then say the plugins do not work. There are many plugins that break. Check first and if you need to contact the author, ask nicely :)

    Plugins II
    Deactivate plugins before upgrading. If you do not you may get errors and the advice here will be to delete those plugins. Your choice.

    Problems ?
    If you experience any, post to this thread. Please give us lots of information such as:
    Your site
    Your host
    The precise error
    What you have done to try and mend the blog
    If you really did follow the full upgrade instructions. We can tell you know... :)

    Also, do not just say "I have the same problem" as someone else - you probably haven't - you should state your problem in full, along with what you have done.

    And please remember - all the help you get here is provided by other members.

    (from the wonderful Podz)

  2. allotherplaces
    Member
    Posted 8 years ago #

    Thanx Podz

    I have a question about the definition of 'Multi-user blogs'

    Do you mean like mu.*

    or do you mean like changing: $table_prefix = 'wp_' to 'something_'

    I posted this question at
    http://new.wordpress.org/support/topic/53212

    thanks for your pre-emptive assistance! :-)

  3. Mark (podz)
    Support Maven
    Posted 8 years ago #

    You can change the table_prefix and have several blogs in a single database - that's still fine.

    But One Install and lots of users ? mu.wordpress.org :)

  4. allotherplaces
    Member
    Posted 8 years ago #

    thanks again podz...

    but to be clear, (i dont want to mess this one up) lets say I have ten multiple 'blogs_' running now - and want to try 2.0 on 'blog03_' - do I have to back up ALL the others at the same time, or can I just do 'blog03_'

    thanks again for your patience :-)

  5. Mark (podz)
    Support Maven
    Posted 8 years ago #

    10 blogs in one database ?
    And JUST one you want to upgrade ?

    Backup just those tables used by the blog you are going to upgrade. (Though backing them all up is a Good Thing :) )

  6. Michael Bishop

    Posted 8 years ago #

    Each database and core set of files should be backed up before any upgrade is done. If they are each independently running their own DB, then only #3 needs backing up, but remember, as it's a current mantra, you can never have enough backups.

  7. Jewels
    Member
    Posted 8 years ago #

    Is it possible for me to do a clean install and then upload a backup from 1.2.2?

    I'm changing the site name (and hence database name) too, so I'm wondering if that would throw all the permalinks off or something.

  8. Usayd
    Member
    Posted 8 years ago #

    Great work with the release and the website guys, I set up a tester at http://yse-uk.com/wp2/, working great.

  9. mattman
    Member
    Posted 8 years ago #

    Jewels,

    A clean install is possible but not entirely in the sense you thought.

    1. BACKUP EVERYTHING, I know it's been said but just incase :)
    2. Delete all files and folders where your old WP install was - EXCLUDING wp-config.php and the wp-content directory.
    3. At this stage, create your new database and upload the sql file you will have got from your database backup.
    4. Go back to your wp-config.php file and modify it to match the new database details.
    6. Upload the new files that come from WP2.0
    7. Run the wp-admin/upgrade.php script.
    8. Go into your admin panel and change the site name in options.

    That should all work :D BACKUP!!!<>

  10. Working like a charm on my site! :)

  11. amacgenius
    Member
    Posted 8 years ago #

    I'm having extreme trouble, I restored my 1.5.2 db, and now I can't access my wp-admin panel so I can de-activate all my plugins before attempting the upgrade again, this is the message I get.

    Fatal error: Cannot redeclare generate_page_rewrite_rules() (previously declared in /home/genius/public_html/wp-includes/functions-post.php:787) in /home/genius/public_html/wp-admin/admin-functions.php on line 559

  12. yanis
    Member
    Posted 8 years ago #

    "1. BACKUP EVERYTHING, I know it's been said but just incase :)
    2. Delete all files and folders where your old WP install was - EXCLUDING wp-config.php and the wp-content directory."

    There's an easier and 'safer' way -- again backup everything, (obviously, it's just plain foolishness to do this without a full backup), then rename the original top level wordpress directory (or move it into a new directory). This leaves everything intact (the db included, read on for that), a simple rename & 5 seconds later the 'old' blog is back - no "risky" recovery needed.

    Download and extract the new WP 2.0 version. If one has access to phpmyadmin then life is easy - backup the existing database (try and minimize taking the 'cruft', plugin tables and the like can be recreated as needed by the plugins.. the idea is to give the upgrade process the best chance of success) - open it in a text file and do a 'search and replace' for the prefix (e.g. wp_) and replace with something like new_. Create a new db, import the modified sql back in, update the wp-config.php with the new prefix and then perform the wp-admin/upgrade.php process.

    This all has some nifty advantages:

    1) the original files remain intact - reversal takes 10 seconds to rename the new and old directories
    2) the original db (and any additional tables) is still available without a restore (very handy)
    3) the new db can be worked on without impacting the existing blog db (a restore is only as good as the last backup made). ;)
    4) one can run concurrent (old + new) blogs to keep a web presence if "diving in the deep end" is a scary thought.

    With this process one is not deleting or modifying any part of the original blog - it's all intact and 5 seconds of renaming will bring it back. Having the old and new blogs on the go is also useful if one is going to do a more 'full on' layout change.

  13. yanis
    Member
    Posted 8 years ago #

    I'm having extreme trouble, I restored my 1.5.2 db, and now I can't access my wp-admin panel so I can de-activate all my plugins before attempting the upgrade again, this is the message I get.

    You'll need to downgrade the wordpress files as well. Might be worth doing a full restore (db and files) then disabling all your plugins before an upgrade (or have a read of my lengthy (heh. sorry) guide above for an alternate solution to upgrades).

  14. Yep, WordPress 2.0 is not backwards compatible database and file wise, hence the version step.

  15. Hypercubed
    Member
    Posted 8 years ago #

    Ahhhhh! Installed wordpress 2.0 and everything looked fine. Went to reactive plugins and they ALL fail. I don't mean they are not compatible. I click the activate link and the browser reports “Plugin Activated�… but it is flat out lying. No matter what I do no plugins are not activated. Even Akismet plugin supplied with WP 2.0 doesn't activate. HELP?!

  16. amacgenius
    Member
    Posted 8 years ago #

    I reactivated my plugins and now for where the author name should be it gives me this:

    WordPress database error: [Unknown column 'user_level' in 'where clause']
    SELECT COUNT(*) FROM wp_users WHERE user_level > 1

  17. Sounds like one of your plugins is not WordPress 2.0 compatible (the user level system has completely changed in this new version).

    See this thread: http://new.wordpress.org/support/topic/49917

  18. mndoci
    Member
    Posted 8 years ago #

    Yahoo Web Hosting set up my account automatically with an RC for WP 2.0 and will upgrade automatically to WP 2.0. Do I need to do anything specifically, or will Yahoo take care of the upgrade behind the scenes?

  19. Jewels
    Member
    Posted 8 years ago #

    Ah ok. I installed everything on a new site (the old blog is in tact). The problem is now I can't access my new admin panel; it just keeps redirecting back to my old installation.

  20. Jewels: unless you made a copy of your database before upgrading, there is no sense in keeping your old copy. The upgrade broke your old install as the WordPress 2.0 database structure is NOT backwards compatible.

  21. Michael Bishop

    Posted 8 years ago #

    Yahoo Web Hosting set up my account automatically with an RC for WP 2.0 and will upgrade automatically to WP 2.0. Do I need to do anything specifically, or will Yahoo take care of the upgrade behind the scenes?

    You will have to contact Yahoo for that, we only handle support for individual installations of WP on personal domains. Sounds like a hybrid of fantastico. If you are running a RC without problems, I'd simply leave it until yahoo handles it on their end, especially not knowing the full details of how the installs go, there.

  22. Michael Bishop

    Posted 8 years ago #

    jewels, did you change the URI in the blog before you moved it to a new domain? If not, you may have to delve into the world of MYSQL to change the URI. Report back on the change, and we'll be able to direct you to the proper resource.

  23. yanis
    Member
    Posted 8 years ago #

    The problem is now I can't access my new admin panel; it just keeps redirecting back to my old installation.

    If you copied the entire db, then it still has your old settings. One quick fix is to (wait for it) make sure you have a copy of the options table - then delete the options table (i hate recommending deletion btw ;).

    re-run the upgrade and the options table will be re-created (with default settings).

    .. or - you can risk it all and hack the DB via phpmyadmin or the like (which I'm not a big fan of). :D

  24. Jewels
    Member
    Posted 8 years ago #

    Ouch. No I never did change the URI. How easy would it be to change it directly?

  25. Michael Bishop

    Posted 8 years ago #

    Jewels, take a look at this link, and if it seems like something you feel comfortable tackling..if not, check back here, and we can find another solution. Just make sure you keep the backups handy, as they may come into play soon.
    http://www.tamba2.org.uk/wordpress/site-url/

  26. Jewels
    Member
    Posted 8 years ago #

    Should I change the site URL before or after running upgrade.php?

    I emptied the database and re-uploaded a backup since my old installation was affected somehow (it's on a completely different site with a different database, user and password so how it broke it beyond me).

  27. Michael Bishop

    Posted 8 years ago #

    Jewels, try this tutorial
    http://www.tamba2.org.uk/wordpress/move/

    it's for moving your blog to a new domain.

  28. Jewels
    Member
    Posted 8 years ago #

    I have everything working fine on my new domain now. I guess I could just delete my old installation, although I don't understand why it broke.

    Thanks for the help.

  29. yanis
    Member
    Posted 8 years ago #

    I guess I could just delete my old installation, although I don't understand why it broke.

    If you did a backup and restore or copy of the wordpress db, then the original settings will go with it - which might point to the old location - which will be incorrect if there is a new location for the wp files.

  30. solidfan
    Member
    Posted 8 years ago #

    I followed the tamba2 guide (quick version) and it worked just great. Thanks a lot!!

124

Topic Closed

This topic has been closed to new replies.

About this Topic