Site Overwritten After Renaming and Cloning, Stuck on Provisioning

Support
1

Issue Summary

I had a fully functioning one-page site setup in Local named “mysite.com”.
I’m redesigning the site so I renamed the original site to “mysite.com one-pager” then cloned it, naming the clone the same as the old “mysite.com”.
The cloning got stuck on “provisioning” for hours. I was able to right-click delete it but now the original site doesn’t work. Under Database, there are error messages “Unable to find DB_”… I check /Local Sites and only /mysite.com exists and inside /app, only /sql folder exists. The rest has been deleted. Looks like there’s a bug in renaming a site then creating a new one with the same name.

Troubleshooting Questions

  • Does this happen for all sites in Local, or just one in particular?
    Just this one.

  • Are you able to create a new, plain WordPress site in Local and access it in a Browser?
    Yes

Replication

Describe the steps that others can take to replicate this issue. If you have screenshots that can help clarify what is happening, please include them!

System Details

  • Which version of Local is being used?
    5.9.3+5100

  • What Operating System (OS) and OS version is being used?

    • For example: macOS Catalina or Windows 10 Professional
      Catalina

  • Attach the Local Log. See this Community Forum post for instructions on how to do so:

localwp1
localwp12400×1600 319 KB
localwp2
localwp21068×858 73.3 KB
localwp3
localwp31118×760 85.5 KB

local-lightning.log (961.8 KB)

2

What I think happened is that renaming the site only changes what it’s called within the Local UI. The actual folder and domain aren’t changed when renaming the site.

When the clone was started and the original name was used, Local became confused because it was asked to clone itself onto itself (since the folder name was the same).

I’ll be sure to write up a bug so that this gets fixed in future versions of Local!

In the interest of trying to restore the original site, can you try using the files for the site by following the steps outlined in the “Restoring From Only Local Site files” section of this help doc:

4

That makes sense, thanks for the reply.
I just took the live copy and created a new Local site and migrated it there. No big deal, it’s good to see it is a bug and you’re on it. Cheers!

1 Like
5

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.