cbhurji

I am sorry but I don’t seem to quite fully understand what you are stating in first or second paragraph

If it was not clear then here it is again:
You run installer..blah..blah.php on the live or localhost and PAUSE at the point of path replacement. Go into phpadmin; select ALL entries in your DB (remember this the DB that the current installer has just overwritten into); perform DROP on ALL; open your original SQL packed by either you OR Duplicator (either will work); Perform IMPORT and you will get back all your entries; If you care to note the number of entries BEFORE DROP and after IMPORT you will see a discrepancies, proving bug in plugin; now go back to PAUSED installer script and run to end and let it completely

This has worked 100% for me and I have done it over 50times by now (frantic webpage designs). I do like the simplicity of the plugin and cannot be arsed to go find another (YET!). I have informed the designer of this issue and he has NOT bothered to reply back. I have upgraded with all his latest bug fixes and can still confirm it is BROKEN but my manual intervention still works for me so I made it my norm regardless of the updates from designer ??

Try exactly what I am suggesting (do not deviate with your own) and see you get on with it

I have already informed the developer of his plugin not working and since there has been several releases but not any of them have managed to fix my problem (possible others similar ones). I have just tested the latest and found almost 75 entries missed out from my latest install!
However I have do like the simplicity of this plugin and found a not so difficult workaround for this. Try this:
1) Run your Duplicator and generate all the files as normal
2) Copy your files (I normally just do sql, php and zip files) and start the installation on your live or local server
3) You obviously would have initiated a new database (eg testdatabase entry), which will get filled by the installer
4) STOP at the point where it is going to replace your paths and names on the installer. Open your live OR local phpmyadmin and locate your database (ie testdatabase). Select all the entries and note the number of total entries (for verify missing entries)
5) Select DROP functionally with all entries selected.
6) Select import in phpmyadmin and browse to the sql file you first generated using Duplicator and import in manually
7) Go back to testdatabase and select all entries and see how many entries there are now and you should see LOTS more than in step 4
8) Go back to your Duplicator installer window and continue with the replace paths/name process and let it complete to the end and do all the necessary usual step
9) This works for me 100% times showing a buggy import functionally of Duplicator

Hi Cory,
I have discovered something interesting with your plugin that you might help you home in the problem

As it has been a while, you might want to re-read the issue, but if you remember the Duplicator plugin would normally miss out entries for my issue? Well I have found that it is importing stage by your plugin that is going wrong.

It somehow does not seem to be an issue running on live server (Linux OS with different WP, blah, blah as explained previously), but when I try to install my website on my localhost (PC x86 system – Win10 64bit) then problem occurs. So what I did, was to run up Duplicator in the normal way but at the point just before the plugin is about to carry out search/replace directory path, I manually used the import function in phpMyadmin and reinstall the “same” SQL database from the Duplicator packed files. I then ran to the end of Duplicator installation of website i.e. normal steps etc. and everything worked!

I believe what might be happening is (depending upon which platform) the import function of SQL database might be detecting some sort of error and the plugin gives up at first error and hence incomplete database. I believe some other customers have also mentioned missing entries and might the same issue.

You might want to look at your error handling routine ….

Hi Cory,
After a lot of frustration from debugging, I can say that your Duplicator plugin is buggy i.e. when moving from live server-to-localhosts on a WAMPSERVER (whatever version). Seems OK when moving localhost-to-live server (but not entirely convinced about this as well as I just do not have time). My live server is UNIX OS but localhost is x86 OS so I think this could be additional issue somewhere down the line

To prove this, I manually tried to export/import database, using WAMPSERVER 3.0.4 and this was buggy as well! This version throw up some errors on this exercise. I then tried downloading latest WAMSEVER 3.0.6 and this resolved the issue of manual export/import BUT your Duplicator plugin does the same.
I think you suppress the errors within your plugin and continue with database as much as possible, but in doing so you miss out entries tables as I counted incomplete tables. With the latest WAMPSERVER 3.0.6 manual testing, I can get correct table entries but your plugin fails to do this correctly still. I had wp_users missing but I suspect that depending upon no of entries, your plugin gives up and could have more missing then I can see.

I have decided to revert to manual porting as I have wasted a few weeks chasing this issue (yet another learning curve!).

I hope Window servers user to be careful as well on this…..

Hi Cory,
The problem is on my localhost back on my PC and I do not see how we can do this. As I mentioned I do not seem to have this particular issue when I transfer from localhost-to-live. Therefore, I do not see login in offline is any useful

1) I have not also seen any YouTube or instruction out there showing Duplicator for localhost-to-localhost copies, which makes me think that this side might be buggy. I have already asked you this before, but you do not seem to have answered it. Please let me know that Duplicator has been tested local-to-local and works for you?
2) I have used an export/import method to copy “wp_users” entry from another database and managed to login into WP, but the site (on localhost) was semi OK, however messed up with missing items on pages, etc. Can you post me the correct method in creating this “wp_users” entry manually?

Just to add that I have been testing this issue most of the day today and have tried a different WP website, which was designed a while back

It seems that Duplicator worked from me in the past when I wanted to transfer from localhost-to-live, but now I have discovered that it does not work correctly (i.e. missing wp_users and perhaps more until I get past this issue, I can’t tell), when 1) transferring from live-to-localhost OR 2) localhost-to-localhost.

I would have thought it would be very easy for you to check this on your end with any site for a test.

PS: I tried copying wp_users from a different database, but this gets me logged in but the website is messed up!

Hi Cory,
To keep things simple over the web Q&A, I decided to “clean” out and try the Duplicator files again, to transfer from localhost-to-live server. I wanted to make sure I have a complete set of files to share with you if need be.

BTW: this installation is the one I am having problems with when transferring to live server, i.e. different error to what we talking here, as I was getting “Error 500”, which the support team is still looking at.

So this is how it all started for me, where I decided to test out the duplicator archives files back on the localhost to do some debugging myself, while waiting on the server support team

The results are as follows:
On Live server: No problem when the files are extracted, I can see “wp_users” entry created but as I mentioned when I try to save the permalinks on the live server, it crashes with Error 500
On localhost: With the same files extracted, I DONOT see “wp_users” entry and cannot proceed to logging into WP. The test directory does seem to have all the necessary files. I am finding a way to manually create an entry so that I can verify that the Duplicator files work on localhost, before I beat on the support team door

To answer your ques about checking the log file ….I did and it was clean with no errors showing and only about 3KB. Shame I can’t attach it here for your attention, as I don’t see upload option

Sorry I understand (newbie to this forum) and posted on the link you provided