vons

Hello again,
Sorry for the wait, but there’s been a lot going on which has kept me from going forward with this.

Thankfully, it all went with a breeze! Here was the process:

Deleted the old _2_ tables (in phpMyAdmin after backing those up)
Deleted the “new” subsite with ID#3 in the network’s website page
Deleted its leftover /3/ uploads folder in /wp-content/uploads/sites/
Deleted its _3_ tables (again, in phpMyAdmin after backing those up)
Created a new subsite with the “old” name and URL
Success!

Hopefully this’ll help another perfectionist in the future who’s annoyed with incrementing ID’s in the uploads folder, DB etc.

Big thanks again @bcworkz for the help and trying it out yourself, really appreciate it!

No worries! I’ve had a couple of things myself.

Great! Sorry if it sounds like I’m repeating myself, it’s just been a pretty terrible experience with this site moving project. And I was just a bit surprised that this process was so straightforward compared to the other things that have occurred.

Thanks again, I’ll get back to this thread when I get around to moving forward with this part!

@bcworkz Not to bombard you with more replies, but just to make sure I’ve got the process down(and for future reference) ??

1a. Delete the abandoned tables from the old 2nd subsite
1b. Delete the 3rd subsite, its uploads folder and its abandoned tables
1c. Delete anything in wbesite_blogmeta?
2. Decrease the AUTO_INCREMENT option on the website_blog table(in the operations tab in phpMyAdmin)
3. Create a new site on the network screen
3a. Change the URL/slug post-creation in-case it won’t let me re-use the old one.

Ah, I see.
So I could run into some issue with that on the “Create new subsite” screen after lowering the increment value, but if I do I can just edit it right after? I was planning on using the same https://example.com/subsite URL as the deleted 2nd and current 3rd one.

Not to bother you even more, but was there anything in the website_blogmeta table when you tested it out?
Thanks!

Potentially dumb question, but what’s the difference between the subsite URL and slug?

Ah, so I should definitely be in the clear on that end since I have no other subsites apart from the (soon to be deleted)3rd one? And after cleaning out the website_2 and _3’s plugin tables.

Again, thanks for trying everything out!
I feel a lot more confident moving forward with this now. I just want to work out any potential hiccups so I don’t need to deal with a broken installation.

Ah, thanks for trying it out!

Do you mean the name of the blog or the URL? I currently have the 3rd subsite using the deleted 2nd one’s name and URL, was planning on re-using it again for the “new” 2nd one after resetting the AUTO_INCREMENT. So that won’t work?
I’ve read some StackOverflow threads about AUTO_INCREMENT, they’re pretty old but most of them say it’s not possible to lower the value from your current highest. But since you were successful I suppose that’s no longer a thing?

Our host offers a separate DB backup as well, I guess if anything really does go irreversibly wrong I’ll just restore that and the file backup. But I think it’s like you mentioned, there’s probably not much that really could do that.

I’ll see if I can find someone else with experience doing this around the web, and then I’ll get back here in case anyone else wants to reset their multisite ID’s.
I’m a little bit surprised there’s not more about this anywhere else, but then again I guess most people really wouldn’t care about a ID in their database and uploads folder.
Thanks again!

Alright, I’ll take a backup of the leftover _2 and _3 tables as well just to be safe before I delete them, I’ll check out wp_blogmeta too. But it seems like WP did a good job scrubbing off the old subsite, sans the leftover plugin tables and the uploads folder in /sites/ID/. And apart from this, it should be safe to proceed?

I’ll take a full backup of the entire DB as well, and I’ll see if I can find anyone else who has experience with this just to be on the safe side. Seems like the author of the linked article in the first post deleted it some time after I created this thread..
Thanks again, much appreciated!

Ah, got it!

Unfortunately I lost access to the WP All-in-One plugin when I converted the site into a multisite. Our host has a backup feature, but I’m not too sure how well it works with WP. I’ll do a DB backup, hopefully nothing goes wrong.

Sorry to keep bothering you, but is there anything else I need to do DB-wise? I’ve yet to come around to deleting the old site’s tables, but there shouldn’t be anything else I need to clean up after that and the soon-to-be-deleted third site, right?
Thanks again, really appreciate it!

Thanks for replying!
So it should be safe to decrease considering the fact that the 2nd subsite was deleted? There’s a couple of abandoned plugin tables from the 2nd(and probably from the 3rd subsite) after I deleted it, but I’ve confirmed with the plugin devs that it should be safe to delete them(since their respective subsite is gone).

Found the AUTO_INCREMENT option in the Operations tab, that method feels a lot better than running SQL! It’s set to 4 right now, should it be on 1 or 2 when I create a new subsite?

Do you have any backup plugins you could recommend for multisites? Or Should I just make a manual one in phpMyAdmin?
Thanks again!

Got it, thanks!

I’ll do that, thanks.
I was just more curious how this plugin handles the restore process. If it “wipes” your uploads folder, then fill it in with the items from the backup or if it just “dumps” everything back, which may cause issues for me.

@yaniiliev Sorry to bother you with another question, but there are quite a few images that were moved around that had new thumbnails generated and the old ones got abandoned by WP. A few of these abandoned thumbnails laying around the uploads folder were in use and registered in the old backup, is this going to cause any issues if I were to restore? Should I remove any current abandoned thumbnails before restoring?

Thanks again!

• This reply was modified 4 years, 3 months ago by vons. Reason: Clarification

Great, thanks!

Hello,
This isn’t directly related to the plugin, it did its job and the error was on my side. I just wanted to give a background to what I was doing.