@jnashhawkins Thank you for taking the time to respond.
I’m going to figure since you mentioned a blog ID that you are running multi-site.
Yes, that is why I posted in “Networking WordPress” ??
Just restore from your last good backup.
Unfortunately, that is not an option as it would regress all the other bloggers (i.e. all the other networked blog sites). What I wanted to do was extract just the tables for the affected blog site (and do a delete and import on just those); however, I only do occasional work for the company owning the Networked WordPress installation and the last backup I did was 14 months ago. I am going to contact the owner and see if they have a recent backup (and if not, remind them about taking backups!).
And, just in case, I’d probably do an optimize on my database (with a full backup in hand).
Yes, generally good advice. I needed to do that a few years ago, but I think that since then the WordPress team fixed the problem that caused a failure to reclaim space on deletion.
I’ve had a few odd problems with individual sites of a multisite network over the years where they seem to get flaky. Just one of the many sites usually, and it just happens for no discernable reason.
I have not run into this. I use sub-domains to handle Networking. In my opinion it seems to be cleaner. If you are use the other method (directories), it might be less robust (not a fact, just a surmise).
My usual response is to migrate the ‘flaky’ site to a new site on the same multisite though I have in the past migrated sites from one multisite install to another. Just leave the old site ‘as is’ for a time, migrate and remap the domain name as needed. Later on you can delete the old site or empty it and repurpose.
Sounds a bit awkward. There are a number of potential problems with this approach, including just migrating the “flakiness”. Mind you, what I want to do (if there is a recent backup available) also has some potential pitfalls. I think I might have to hack the entry for the blog site in one of the base site’s tables.
Another thing to watch for is server timeouts on a multisite. If your database is on that same box you’re risking the database integrity somewhat.
Different servers, so not a problem.
-
This reply was modified 5 years, 8 months ago by johngoold.