Yep, running into the same issue. Looks like Duplicator unpacks the physical files but the database installation creates a table named “wp_duplicator_packages” and fails to install the actual database. WordPress doesn’t see a valid WP database, so it falls back to the new install protocol. This has come up on all of our sites since 4.2 on two different workstations.
Staying at WP 4.1 also avoided the issue for me, but if you’ve already upgraded to 4.2 it’s hard to get that genie back in the bottle.
I also experience freezes whenever I try to package a Roots/Sage theme with the current version, which may or may not be related.
Same problem, good to see I’m not the only one. so for now the only workaround would be to roll back WordPress to 4.1…yikes.
I’m running version 4.2.2
I take a copy of the localhost and I can recreate on the localhost – no issues.
But when I move it from the windows localhost to linux server I get prompted to install WordPress again. I went through the process to see the issue and nothing is created per this plugin.
4.1 is not the solution; but I guess in the meantime.
help us & save our souls!
Hey Guys,
I haven’t been able to reproduce this issue on my sites with 4.2.2. Has anyone been able to reproduce this on a base WP install without any other plugins installed? I remember a similar thread about 6 months ago where a specific plugin the user had installed was triggering the the WP installer. Can someone double-check in there server environment if they can re-pro this with a base WP install?
Cheers~
We’ve tried it with two different installs, and though they both had some added theme based functionality they didn’t share any plugins between them outside of the default ones. Have not tried a straight up vanilla WP install yet, will try when I get some free time to.
I performed a fresh install. Using the base theme as I usually do. No other plugins, no mods. And fails as noted above.
I back-up and moved to the server online from my localhost and got prompted to re-install WP after placing in the database details.
Tried the same with 4.1.5 and worked as it should. Anything newer it fails.
Thanks for the update catchfirecreative! If you could also try one of the base WP themes that would help (just to rule out a possible theme issue). If you still get the issue go ahead and submit a support ticket and I’ll try and look at it when I can get some free time. Be sure to refer to this thread in the ticket.
Thanks
Ok – Localhost to Localhost works for me. The same server to the same server works also. The server back-up to my localhost works. This is all under version 4.2.2 and the Theme is Twenty Fifteen.
The fail for me is localhost to online server using 4.2.2, 4.2.1 & 4.2.
4.1.5 works 100% (but I’re prefer to use a current one instead of having to upgrade on the server)
The same for me.
I’m using Duplicator from localhost to server. Localhost WordPress is version 4.2.2 using MAMP.
I can’t downgrade the local installation so everything is a mess…
Thanks for your support.
I’ve also been using MAMP for the local installation. Could that be the common factor?
I’m using MAMP version 3.0.7.3.
WordPress 4.1.5 works OK from localhost to server. No MAMP updates or configurations changed at all.
Just in case this info can help…
Thanks again.
Are you guys using mysqldump as the db build option? I think for some reason the database.sql file inside the archive.zip is not getting created on your systems for some reason.
Can you validate if this file is getting generated properly for you? Also possibly try the PHP database build mode for 4.2.2 and see if that gets you an different result set for the database.sql file…
Thxs
Hello Cory.
The database.sql is in the .zip file. What should we look at?
Hey bigbank,
I was going to have you check and make sure it had SQL statments in it, and that it wasn’t empty. However it looks like this issue may be a problem with some older databases. In the latest version WP did an update to older DB schemas. The work-a-rounds for these fixes are found at these links:
Manually rename in SQL
Coded sample to rename
Hope that helps!
Ok thank you.
I did a compare of the database.sql files and saw the differences.
Is there going to be an update to the plugin to avoid any manual intervention? Just curious.
