If you create a blueprint from a multisite installation, then any sites built from that blueprint will redirect to the original installation.
For example, make a new multisite (subdirectory) local site called “TestMU” with a domain name of “testmu.dev”. This should work fine.
Now ask Local to make a blueprint from that local site.
Finally, create a new local site called “TestMU 2” and use the blueprint you just created, it should have the domain name “testmu-2.dev”. No errors will be reported.
Now try try to visit the second site, testmu-2.dev. You will be redirected to testmu.dev instead.
Something seems to be wrong about how Local deals with multisite.
Huh. OK. That kind of makes blueprints much less useful. I would hope that in the future they are smart enough to search-replace domain references automatically as part of a setup from blueprint. Or at least warn the user that this critical task is left undone by blueprints. But thanks for the pointer!
However, there are a few things missed searching and replacing with multisite in the current version of Local. The fix has already been written and implemented in an upcoming version of Local
Super! Looking forward to the upcoming version then.
Thanks for all the effort put into Local. It feels like magic, which is, I guess, why it is so jarring when something does not work. The team is doing a magnificent job for the community and I am very grateful that you share this so openly with the WordPress community.
