WordPress.org

1. thelaw
   Member
   Posted 4 months ago #

   Would be very grateful for all assistance with this problem!

   I remember creating a wordpress multiuser site a long while ago. I deleted the first blog and didn't think twice. The tables that it must have deleted were the wp_table entries. The next blog/site was created with wp_1_table and so on. Despite this, the site has worked flawlessly. Unfortunately I've noticed that the table numbering is not what some software is expecting - it is expecting at least one complete site under "prefix_table" format consistently for the first site/blog. My site is split up. I need to switch the wp_1_table prefixes to wp_table so that it's compatible. I tried to follow some sites instructions but they don't work and seems as though something is looking for the wp_1_table tables.

   The full table names for a stock install look like this before you start adding multisites:

   wp_commentmeta
   wp_comments
   wp_links
   wp_options
   wp_postmeta
   wp_posts
   wp_terms
   wp_term_relationships
   wp_term_taxonomy
   wp_ucan_post_submissions
   wp_usermeta
   wp_users

   My Database structure:

   wp_blogs
   wp_blog_versions
   wp_registration_log
   wp_signups
   wp_site
   wp_sitecategories
   wp_sitemeta
   wp_usermeta
   wp_users
   wp_1_ahm_download_stats
   wp_1_ahm_filemeta
   wp_1_ahm_files
   wp_1_commentmeta
   wp_1_comments
   wp_1_links
   wp_1_mban_banner
   wp_1_mban_options
   wp_1_mban_zone
   wp_1_mobilepress
   wp_1_options
   wp_1_postmeta
   wp_1_posts
   wp_1_terms
   wp_1_term_relationships
   wp_1_term_taxonomy
   wp_4_ etc.
   wp_9_ etc.

2. thelaw
   Member
   Posted 4 months ago #

   There has to be a way to fix this. I'm wondering if there is a way to be able to export individual sites and import them into a brand new wp 3 install. I just can't seem to find a way and the export/import option doesn't take into account many things such as plugins, etc. which could make for a nightmare.

   Anyways, if someone could lend some help on moving the wp_1_ tabels back to wp_ and so that will be the first install, I'd be grateful. It's remarkable how many plugins assume that is the way it works and surprising that WP allows you to delete the first blog and remain with some consequences of splitting up important data. Not necessarily WP's fault but you know what I mean...

3. thelaw
   Member
   Posted 4 months ago #

   Here is one post that exemplifies part of the problem:

   http://wordpress.stackexchange.com/questions/25001/mu-root-blog-options-table-after-3-0-upgrade-wp-options-or-wp-1-options

   When I converted to WP 3.0, I'm not sure if the schema is "proper" as it should be.

4. thelaw
   Member
   Posted 4 months ago #

   I fixed this. It wasn't easy. Apparently separation of tables like this can arise from using WordPress MU and converted to 3.x and also as a result of not such great config instructions here, despite the Codex. The Codex can be a surprisingly large amount of information displayed very poorly when it comes to just seeing what working examples should look like.

Reply

You must log in to post.