Support » Fixing WordPress » db upgrade error, but i didn’t upgrade

  • Resolved pufftenticle

    (@pufftenticle)


    out of the blue this afternoon, i began to (at first) receive this error:

    WordPress database error: [Duplicate entry '998' for key 1]
    INSERT INTO wp_post2cat (post_id, category_id) VALUES (723, 5)

    anytime i tried to publish a post. i came to the forum, searched, and found many different possibilities as to the cause, but all had to do with the upgrade to 2.3 (which i did NOT do – nothing has changed on my install, theme, or plugins)

    after deactivating the google sitemap, as suggested in many of the posts, i then began to receive the famous header error message:

    Warning: Cannot modify header information - headers already sent by (output started at /homepages/0/d144193462/htdocs/texas-fire/wp-includes/wp-db.php:121) in /homepages/0/d144193462/htdocs/texas-fire/wp-includes/pluggable.php on line 275

    i followed each of the suggestions and the codex step by step on the header issue, and it is still present. i was using an older version of the sitemap generator, so i went and got the newer version, which then added this error into the mix:

    Warning: mysql_affected_rows() [function.mysql-affected-rows]: A link to the server could not be established in /homepages/0/d144193462/htdocs/texas-fire/wp-includes/wp-db.php on line 183
    
    Warning: mysql_affected_rows() [function.mysql-affected-rows]: A link to the server could not be established in /homepages/0/d144193462/htdocs/texas-fire/wp-includes/wp-db.php on line 183
    
    Warning: mysql_affected_rows() [function.mysql-affected-rows]: A link to the server could not be established in /homepages/0/d144193462/htdocs/texas-fire/wp-includes/wp-db.php on line 183
    
    Warning: mysql_affected_rows() [function.mysql-affected-rows]: A link to the server could not be established in /homepages/0/d144193462/htdocs/texas-fire/wp-includes/wp-db.php on line 183
    
    Warning: mysql_affected_rows() [function.mysql-affected-rows]: A link to the server could not be established in /homepages/0/d144193462/htdocs/texas-fire/wp-includes/wp-db.php on line 183
    
    Warning: mysql_affected_rows() [function.mysql-affected-rows]: A link to the server could not be established in /homepages/0/d144193462/htdocs/texas-fire/wp-includes/wp-db.php on line 183
    
    Warning: mysql_affected_rows() [function.mysql-affected-rows]: A link to the server could not be established in /homepages/0/d144193462/htdocs/texas-fire/wp-includes/wp-db.php on line 183
    
    Warning: mysql_affected_rows() [function.mysql-affected-rows]: A link to the server could not be established in /homepages/0/d144193462/htdocs/texas-fire/wp-includes/wp-db.php on line 183
    
    Warning: mysql_affected_rows() [function.mysql-affected-rows]: A link to the server could not be established in /homepages/0/d144193462/htdocs/texas-fire/wp-includes/wp-db.php on line 183
    
    Warning: mysql_affected_rows() [function.mysql-affected-rows]: A link to the server could not be established in /homepages/0/d144193462/htdocs/texas-fire/wp-includes/wp-db.php on line 183

    i feel certain everything after the first error is all on me and i can probably toy with it and get it back up and running, but that initial error – any ideas ?

    and again, yes – absolutely not one change at all to the install, db, theme, or plugins in the past month or two.

    thanks

  • The topic ‘db upgrade error, but i didn’t upgrade’ is closed to new replies.