Hi JoeGP, did you have any luck figuring this out? I’m having the same issue. One clue I did discover is that the error is dependent upon the source site, but I could not see any structural difference.
Also having the same issues here. A message to the WP Acadamy guys: I would be more than happy to pay for this plugin if you could promptly support it to be compatible with updated versions of WP etc. I’d even pay a yearly licensing fee just to ensure this thing works when I need it to. It’s such a great plugin when it works! The absolute, tried and true, best of its kind.
Thread Starter
joegp
(@joegp)
@ apdobaj … No, sorry i do not have the time or the talent to fix it, i just used Duplicator instead, it’s more difficult to use but it works and probably always will (because of the way it works), it can neer have conflicts with WP or any themes/plugins.
What you discovered is not what you think (i’m pretty sure). It’s not dependent on the source site but the source sites version of WordPress. Simply put if it’s older then WP 4.0 it will probably still work. If it works on any site using WP 4.0 and later then you might be on to something, but even so, it probably won’t help us.
One way to work around this issue would be to downgrade the version of WP used on the source site but that is even more difficult then using Duplicator and it’s risky.
Unless the author himself responds to this thread (or updates the plugin) we can safely assume the plugin is abandoned. And i read he hasn’t been seen in the last 7 months so yeah…
I’m unsubscribing from this thread, it’s time to move on …
@joegp One site that I’m cloning successfully is running WP4.1.1, so that could be a factor but it doesn’t appear to be the only one. That being said, it could be any number of other things so I’m inclined to take your advice and move to Duplicator – any caveats/words of wisdom that you can share?
