Closed JoshRiser closed 4 years ago
+1, as I'm working on a multisite project right now, and this would be great to have.
Just thought I'd ask if there was any progress with this? I am working on a multisite project at the moment and it pains me to have to do everything manually after using Wordmove for so long!
I managed to have a play today with a multisite install which uses subdirectories (eg. www.domain.com/site1, www.domain.com/site2 etc). Providing the root domain is the same, removing http:// from the Wordmove file and leaving the main domain seemed to work perfectly for me where as it missed parts before.
I don't have a subdomin multisite but may look into this and see if I can edit the code.
Thanks for the update. Im also using a multisite install for clients. @dsgnr could you just explain what you needed to do to make it work with subdirectories?
@dezinerdudes All I did was remove http:// from the vhost and it seems to be able to change the blog and sites table (which don't use http:// or https:// in the domain of those tables so it makes sense given its a standard search and replace) when using subdirectory. I have been using this for the last two weeks flawlessly :)
I have no idea about subdomains though!
Guys this is not going to be supported by the core team. PR are always welcome.
And moreover if you found a working method it would be great to open a wiki page and PR an update to the README.md
if needed.
@pioneerskies that's completely understandable. It's really good that it works with subdirectory multisite though as it is. I keep meaning to have a go at getting it to work with subdomains but never get round to it.
I think a readme/wiki update would be beneficial as it works, just within a limit. I will work on this over the next few days and push a PR :)
I've not been able to get it to work even with a subdirectory install. There are 2 tables that still have to be modified when moving a multisite directoy: wp_site and wp_blogs. They each have a "domain" column that needs to be changed to the new domain.
I haven't actually used sub domain multi site before. Could it work if you changed the vhost in Wordmove to just domain.co.uk? Just emitting http and www.
All I do for sub directory multisite is remove the http part of the vhost and it changed the wp_site and wp_blog tables
@dsgnr I can see how that would work, the issue for me is I don't have my WordPress installations in the main directory of the domains. I.E. on my local server (MAMP) I have a WP installation at localhost/mysite. Then we have a staging server where we upload all of our development sites in subdirectories, so the site would be at dev.mystaging.com/mysite.
In both tables there is a domain and path column, in my example, the domain column would have to be set to localhost or dev.mystaging.com and then the path column would be /mysite/blog1, /mysite/blog2, etc.
From what I can tell, Wordmove just does a find and replace with the vhosts, but in my case the vhosts include the subdirectories, which would have to be split into domain/path parts and updated in those 2 tables.
Honestly it doesn't seem to be that hard of a thing to do... Wordmove just needs to know that it's a multisite installation, and would need to split the vhost paths correctly (if necessary) and update those tables, in addition to the find and replace.
But, I'm not a ruby developer so maybe it's not as simple as it seems.
wordmove 3.2.2 multisite wp_blogs table domain column after pull has production domain instead of localhost domain. Would excluding the wp_blogs table be an option?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I saw this issue that said multisite was not supported fully, however that was posted over two years ago.
I was just wondering what the implementation looks like right now? I am about to develop a multisite platform that will be the first since I started using Wordmove and wanted to see what my workflow will look like as far as pushing/pulling to staging/development environments etc.