Hi
I have just migrated customer blog data from a (flat) WP v2.6.3 site to a WPMu v2.7 site (blog) and observed the following problems/symptoms:
1) i migrated all WP data to the new (almost empty)WPMu environment using mysql phpmyadmin. this is a task i have performed successfully many times before, and although a painful exersize, has always worked ok. it seemed so this time, at first, EXCEPT:
2) i logged into wpmu blog admin, posts categories - although all top level categories displayed ok, NONE of the child categories were displaying!!
3) as a test, i added a new category 'testcat1' and a new subcategory testcat1.1 using the wpmu admin screens - worked ok, AND, suddenly ALL my migrated subcategories suddenly appear in wpmu categories admin screen!!
4) i log in to mysql/phpmyadmin and look at the tables. I find that wp_1_terms.term_id for my new testcat1 category has been set to 2755 and testcat1.1 category has term_id set to 5291!! - it should have been 26 and 27 respectively (the next numbers in autoincrement sequence)!!
5) wp_1_terms NextAutoIndex is now set to 5292!!
6) wp_site_categories table has new entries for testcat1 and testcat1.1, in addition to the existing default install categories Uncategorised and Blogroll. NOTE, i did not add my imported categories to this table since the standard wp site database does not use such a table. i did however, import data into wp_1_terms, wp_1_term_taxonomy and wp_1_term_relationships.
This appears to be a prety scary problem/undocumented feature of wpmu!
it suggests that autoincrement is being overridden in wpmu core code somewhere and also suggests that it will possibly grow exponentially/randomly instead of incrementally under mysql control!
I see several related/identical problems on this forum, going back a year or more, these are:
http://mu.wordpress.org/forums/topic.php?id=6672&page=2&replies=73 - specifically the post by beaulebens on page 2 (and re5et on page 3) comes nearest to explaining it, suggesting that the cause of the problem is the fact that wp_sitecategories table is a legacy table and that wpmu is attempting (unsuccessfully) to maintain two sets of category index, one of which is redundant - something i know from personal coding experience is generally a BAD idea just waiting to blow up!
http://mu.wordpress.org/forums/topic.php?id=3308&page&replies=16 - same problem from 2 years ago
http://wordpress.org/support/topic/29489?replies=23 - same problem from 3 years ago, but this time experienced on wp (not wpmu)
i cant find any refence to this precise problem being fixed or addressed by developers - forgive me if i have missed something/please could you point me there?
can anyone shed some light on how to fix/avoid this AND how to ensure it doesnt blow up at some point in the future (/reassure me that it wont)?
Thanks for any feedback.