clone site redirects to primary site

[cweinhofer]

I created a clone but when I try to use the "open" button, it just redirects to to the main site.

If I manually add the /wp-admin, I can get to the dashboard. Once there, I see an error that "The theme directory does not exist."

Browsing in FTP shows the content folder for this stacked site (content/4) didn't appear to have been created.

[austinginder]

With 8d39c45 the content folder should now be copied during a clone. Want to try it now? Use the attached plugin.

wp-freighter.zip

[cweinhofer]

With 8d39c45 it looks like the content folder is being copied correctly, but I'm still getting that weird forwarding behavior.

• If I create a clone site and then hit the "OPEN" button. The site opens the clone address and then immediately forwards to main site address.
• As above, if I manually add the /wp-admin I can get to the clone's dashboard. With the update, I'm not seeing any errors or anything obviously amiss.
• I also discovered if I try to open the clone address in another browser where I am not logged in to the main site, it opens fine.

[cweinhofer]

The issue persists, and talking with @austinginder it seems likely to be some sort of caching issue. I have found a few more things that seems to help, but whether they work or not seems random -- sometimes they do, sometimes they don't. And ust to be clear, but "doesn't work" I'm meaning "immediately forwards to main site address".

As mentioned above, going to /wp-admin seems to help, but it seems more like going to any specific URL (test1.mysite.com/) is the key. Having said that, it seems like if you want to go to the specific URL of the page set as the WP "homepage", you have to do that for the first time before ever trying to visit the base URL. e.g. If I go to test1.mysite.com/home before ever visiting test1.mysite.com then WP will forward to test1.mysite.com and everything will work fine after that. However if I first try to visit test1.mysite.com it both doesn't work (forward back to the main site HP) and going to test1.mysite.com/home won't work either.

There was some thought of making sure an entry for the subdomain was in the DNS and also registered in the hosting CP (Kinsta in this case). However, I have had at least one occasion where I did both and the site still didn't work after doing that.

There was some discussion of clearing CDN / edge caching, but that has produced mixed results as well.

Clearing the browser cache helped in one case, but not in another. I also tried to flush my OS DNS cache (ipconfig /flushdns in the case of windows), but that didn't seem to have any effect.