WordPress.org

1. GFCphotog
   Member
   Posted 4 months ago #

   Have a WP blog, glutenfreecanteen.com, recently updated to WP 3.3.1. All worked except the admin toolbar. Was creating a beta site as a subdomain, installed another WP 3.3.1 copy, all was fine. Imported the site information using WP Importer to start debugging the problem and the main site's admin page now only goes to the Welcome page for a new install. Also, the new site on the subdomain fails to come live, it seems the import failed, but there is no log data I can locate to say why.

   The wp-config files seem all correct and in their correct locations in the file system.

   Any ideas? The main site is frozen until I can regain control of the site.

   It seems following the advice to install another WP copy in a subdomain of the site was not the best thing to do.

2. GFCphotog
   Member
   Posted 4 months ago #

   More information:

   The new install created db tables _wrd2, the original site's data was in _wrd1 tables. After the import the tables are all messed up, most have been migrated to _wrd2, leaving the non-standard AZIndex and defunct (no longer in use, hadn't deleted the tables yet) WPSentinal tables in _wrd1.

   Any suggestions on how to untwist the mess?

3. GFCphotog
   Member
   Posted 4 months ago #

   So, I then did a full restore from backup, all the files and the db tables, the site is back to where it was. I can limp along like this for a bit, but still need to understand why the subdomain screwed things up.

4. Tim S
   Member
   Posted 4 months ago #

   Was the subdomain linked to the same database? IT sounds as if the issue was that you had two separate WordPress installations using the same database.

5. GFCphotog
   Member
   Posted 4 months ago #

   That was my first thought as well. However the new install created a different database from the first (main) one. The original db was named {id}_wrd1 and the new db that was created used {id}_wrd2. It looks like it was the WordPress Import function that trashed the pair of db's and created the mixed set of tables across both.

   Fortunately, the backup was current. After the backup was restored for the main site's {id}_wrd1 db, both sites now seem to be behaving as expected.

6. Tim S
   Member
   Posted 4 months ago #

   Oh, that's good to hear that you have resolved the issue.

7. GFCphotog
   Member
   Posted 4 months ago #

   Thanks, I might say the main issue regarding the site is resolved, but the root cause is still open. I used a pretty big hammer to fix the main site db. I would still like to understand to understand why it happened in the first place, and get it fixed as I'm sure I'll have to do this again.

Reply

You must log in to post.