Failed Upgrade

  • Resolved Brent

    (@unswolelildude)


    17 years, 5 months ago

    When I tried upgrading WordPress 2.2.2 to 2.3 I get an long page of errors that say:

    WordPress database error: [Duplicate entry ‘2-1’ for key 1]
    INSERT INTO wp_term_relationships (object_id, term_taxonomy_id) VALUES (‘2’, ‘1’)

    Everything seems to work on the site except when I click on a category I get an error on the top of the site that says:

    WordPress database error: [Table ‘wp.wp_categories’ doesn’t exist]
    SELECT cat_ID FROM wp_categories WHERE category_nicename = ‘windows/vista/customization’

    This happened on my “live” website and on a test server. I followed the steps exactly when upgrading both times just as I’ve done since version 1.5.

Viewing 5 replies - 1 through 5 (of 5 total)

  • Those can be ignored.

    – From Ryan (on wp-testers):
    – —-
    Duplicate entry errors when inserting into the term_relationships
    table should not cause any harm. WP 2.2 did not enforce the post_id,
    category_id relationship to be unique in the post2cat table. That has
    resulted in some people having multiple rows for the same post_id,
    category_id pair in post2cat, as Alexander described. The upgrade is
    incorrectly assuming that the post2cat rows are unique. This will
    result in the db error messages but should not mess up your upgrade.

    Thread Starter Brent

    (@unswolelildude)

    How do I stop the second error (in the post above) from appearing on the top of every category page?

    Oops, missed that.

    That would indicate you have a theme (or plugin) compatibility issue as wp_categories no longer is a table in WordPress.

    https://codex.www.ads-software.com/Plugins/Plugin_Compatibility/2.3
    https://codex.www.ads-software.com/Themes/Theme_Compatibility/2.3

    Thread Starter Brent

    (@unswolelildude)

    I’ll give it a shot. Thanks!

    So those errors I get when upgrading WordPress are OK?

    Thread Starter Brent

    (@unswolelildude)

    I figured it out! I was running a plugin called Custom Query String 2.7 that was causing the errors.

    Thanks for the help MichaelH!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Failed Upgrade’ is closed to new replies.