The problem is likely the Domain Mapping plugin. Since the Cloner has to make automatic replacements in the raw data to make sure the new clone sit works properly it needs to operate on a non-domain-mapped site. It should work fine if you:
1) Disable domain mapping on the template / source site
2) Clone the template / source site to the new site
3) Activate domain mapping and configure it on the new clone site
The issue is that the Cloner will clone the domain mapping settings from the source site and those will be set in the clone site and it will conflict with the actual site ID and settings.
Hopefully this tip will help you get this working!
Thank you Never Settle. I did de-activate WordPress MU Domain Mapping and then created a site however the posts and pages were not there in the new site.
I’ll try your exact steps.
How do I “Disable domain mapping on the template / source site?”
Updated detailed in the official support thread.
This turned out to be an issue that none of the sites had Blogname fields filled out. Every site should always have a value in the Blogname / Site Name field for SEO reasons and other reasons. We’re looking into our validation code to help catch this kind of scenario.
Also discovered in the troubleshooting process that having the WordPress MU Domain Mapping by Donncha O Caoimh Network Activated is OK and compatible with the Cloner as long as the source / origin site that you are cloning has NO domain mappings set (when you go to Tools > Domain Mapping it should be BLANK on the site you intend to clone).
Thanks!
Thank you. You have provided the BEST support I’ve ever encountered and I am now able to clone sites VERY efficiently. It’s a HUGE time saving plugin.
