Cloning existing sites results in hung process.
Clone an existing site.
Mac OS 13.4.1 (c) (22F770820d)
Local WP v7.1.0+6396
Local Logs are very out of date for some reason, no time stamps after 03/2023
Hi @tomfinley
Is this happening for any site you try to clone? For example if you create a new, blank site and try to clone that does it still get hung up? Or is it just a specific site you’re trying to clone that doesn’t work?
Hey @Nick-B, thanks for the speedy reply. Blank site cloning works. Larger, “real” sites that I’ve cloned in the past are no longer cloning — they’re stopping specifically at the “Provisioning” stage of the cloning process per the Local fronted, but I can see in the filesystem that /wp-content/ is empty.
Are you running other developer applications simultaneously? Apps like MAMP, XAMPP, or Docker for example.
Do you have multiple sites running when you’re attempting to clone?
How large are the sites you’re trying to clone? Do they have a lot of media content or big DBs?
Are you running other developer applications simultaneously? Apps like MAMP, XAMPP, or Docker for example.
Negative.
Do you have multiple sites running when you’re attempting to clone?
Negative
How large are the sites you’re trying to clone? Do they have a lot of media content or big DBs?
I don’t know entirely know how to qualify this — yes, they’re significantly bigger than blank sites.
However, neither are any bigger than the biggest site I’ve managed to clone locally in the past. However, these sites do share some common characteristics, including a theme that I’ve seen cause some issues previously. Switching themes doesn’t seem to help.
In the course of responding to your message I managed to clone my 2 largest sites. I think there’s some bad code or underlying settings jamming things up.
Disabling Xdebug seemed to do the trick. It’s curious that setting would interfere with some sites but not others. Hanging on errors?
Great find! The main reason we implemented that Xdebug toggle not too long ago was due to it being a known performance burden. Oftentimes when users were struggling with a slow or sluggish experience in the app that was one of the main things to check, but the process for disabling it required a bit of manual work. All that is to say I’m not surprised it did the trick! Since we added the toggle all new sites spun up should default to it being Off automatically. If you run into instances of slowness or things hanging up down the road definitely a good idea to make sure it’s disabled.