Upgrade 2.1.3 to 2.6 Database errors – no wp_terms table etc

Yes, just restored DB and ran upgrade again. These are errors below and as before it says “SUCCESSFUL”. Me thinks this upgrade could be a bit smarter. Do you have any suggestions what would be good steps as I haven’t been following each intermediate upgrade. Perhaps 2.1 -> 2.3 ->2.6?

WordPress database error: [Table ‘indieblog.wp_terms’ doesn’t exist]
SELECT term_id, term_group FROM wp_terms WHERE slug = ”

WordPress database error: [Table ‘indieblog.wp_terms’ doesn’t exist]
INSERT INTO wp_terms (term_id, name, slug, term_group) VALUES (1, ”, ”, 0)

WordPress database error: [Table ‘indieblog.wp_term_taxonomy’ doesn’t exist]
INSERT INTO wp_term_taxonomy (term_id, taxonomy, description, parent, count) VALUES ( 1, ‘category’, ”, 0, 1)

WordPress database error: [Table ‘indieblog.wp_terms’ doesn’t exist]
SELECT term_id, term_group FROM wp_terms WHERE slug = ”

WordPress database error: [Table ‘indieblog.wp_terms’ doesn’t exist]
INSERT INTO wp_terms (term_id, name, slug, term_group) VALUES (2, ”, ”, 0)

WordPress database error: [Table ‘indieblog.wp_term_taxonomy’ doesn’t exist]
INSERT INTO wp_term_taxonomy (term_id, taxonomy, description, parent, count) VALUES ( 2, ‘category’, ”, 0, 0)

WordPress database error: [Table ‘indieblog.wp_terms’ doesn’t exist]
SELECT term_id, term_group FROM wp_terms WHERE slug = ”

WordPress database error: [Table ‘indieblog.wp_terms’ doesn’t exist]
INSERT INTO wp_terms (term_id, name, slug, term_group) VALUES (3, ”, ”, 0)

WordPress database error: [Table ‘indieblog.wp_term_taxonomy’ doesn’t exist]
INSERT INTO wp_term_taxonomy (term_id, taxonomy, description, parent, count) VALUES ( 3, ‘category’, ”, 0, 0)

WordPress database error: [Table ‘indieblog.wp_terms’ doesn’t exist]
SELECT term_id, term_group FROM wp_terms WHERE slug = ”

WordPress database error: [Table ‘indieblog.wp_terms’ doesn’t exist]
INSERT INTO wp_terms (term_id, name, slug, term_group) VALUES (5, ”, ”, 0)

WordPress database error: [Table ‘indieblog.wp_term_taxonomy’ doesn’t exist]
INSERT INTO wp_term_taxonomy (term_id, taxonomy, description, parent, count) VALUES ( 5, ‘category’, ”, 0, 0)

WordPress database error: [Table ‘indieblog.wp_terms’ doesn’t exist]
SELECT term_id, term_group FROM wp_terms WHERE slug = ”

WordPress database error: [Table ‘indieblog.wp_terms’ doesn’t exist]
INSERT INTO wp_terms (term_id, name, slug, term_group) VALUES (6, ”, ”, 0)

WordPress database error: [Table ‘indieblog.wp_term_taxonomy’ doesn’t exist]
INSERT INTO wp_term_taxonomy (term_id, taxonomy, description, parent, count) VALUES ( 6, ‘category’, ”, 0, 0)

WordPress database error: [Table ‘indieblog.wp_term_relationships’ doesn’t exist]
INSERT INTO wp_term_relationships (object_id, term_taxonomy_id) VALUES ( 5, 98)

WordPress database error: [Table ‘indieblog.wp_term_taxonomy’ doesn’t exist]
SELECT term_taxonomy_id, taxonomy FROM wp_term_taxonomy

WordPress database error: [DROP command denied to user ‘savery’@’localhost’ for table ‘wp_categories’]
DROP TABLE IF EXISTS wp_categories

WordPress database error: [DROP command denied to user ‘savery’@’localhost’ for table ‘wp_link2cat’]
DROP TABLE IF EXISTS wp_link2cat

WordPress database error: [DROP command denied to user ‘savery’@’localhost’ for table ‘wp_post2cat’]
DROP TABLE IF EXISTS wp_post2cat
Upgrade Complete

Your WordPress database has been successfully upgraded!

I just ran several attempts to upgrade earlier versions.
I tried 2.2.3 and just 2.2 and both fail with the same results.
I found out my db_version value is 4773. The upgrade seems to delineate at version 4772 and above. This means the routine called is update_old_slugs().
I don’t know if I’m doing this right. I don’t want to re-install the whole site over and over. I have been untaring the archives into directories and then copying wp-admin subtree over the real tree. Then I run the upgrade.php again. So far all attempts give the same errors.
Chris 🙁

I’ve managed to get 2.13 -> 2.2 -> 2.3 to work ok.
But I saw an error relating to user permissions to create table.
I modified the db user permissions to allow ALL operations. And then ran -> 2.3 and it worked. So I’m betting this whole issue is related to these permissions. Typically users don’t give such wide permission to special users for security reasons. I am going to try now -> 2.5 and see if it works.

Thanks for your input.

OK. Success.
I continued -> 2.5 and then -> 2.6.
Got no database errors and have categories back.

My process was like this:

tar up current 2.6 version blog tree
1-untar 2.2 into blog tree
2-chg owners/perms on full tree to work
3-run upgrade.php – make sure no errors
repeat 1-3 again with 2.3, 2.5, and 2.6
then untar my original 2.6 files (there were other edits) in blog tree
so far it looks ok.

Probably this problem was caused by bad db user privileges.

Hope this helps someone else though.

Chris 🙂

Could be. I think what’s needed is that the upgrade.php actually says something like “not successful”. I wouldn’t be surprised if users do these upgrades and see messages but ignore them since they see the result saying “successful”. People don’t really know what to ignore or not.

Perhaps having the script scan the output for key words like “doesn’t exist”, and then outputing a message to let users know it’s not OK. This would have to be smart enough to know which ones are critical and wich can be ignored.

Did further testing and all seems good.

Chris 🙂