Missing wp_users entry from database when moving

Hey @cbhurji,

Can you check the installer-log.txt file. It should be created in the same directory as the installer.php after running the setup. It may have some clues or error entries to help us determine why the table wasn’t created.

Thanks~

Same here, from live to local. In log there are a bunch of errors, including one “wp_users table doesn’t exist”. Aside that, when accessing frontpage, it’s 404.

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

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!

Hey @cbhurji,

If you want to submit a support ticket I can work with you offline to login to your site and see what the issue might be… Please refer to this thread…

Thanks~

• This reply was modified 8 years, 1 month ago by Cory Lamle.

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?

Hey @cbhurji,

1. Yes Duplicator works for local-to-localhost, we perform this operation all the time without issues, so have thousands of other users…

2. There are several tutorials online for moving a single table. Here is one of them.

There can be several reason for why a single table may not copy properly and sometime those items are not easy to spot, for example if the table is corrupted, the default table collation types are not properly setup on the new DB table, and in some cases permissions can cause issues.

The plugin tries to compensate for some of these but in your case something seems to be holding it up. You might have a look in the PHP error or Mysql error logs to see if there are any clues there as well. I do recall a similar issues years ago, but I don’t remember what the actually source of the issue was for that server environment. If I recall they had to update a setting in the my.ini config file.

• This reply was modified 8 years, 1 month ago by Cory Lamle. Reason: spelling

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…..

Hey @cbhurji

The plugin in most cases should log as much as it can to the installer-log.txt, however you are correct there might be issues with your particular combination and without looking under the hood on your environment its difficult to debug via the forums… Its tough to maintain a plugin like this because there are literally millions of different combinations of configurations.

Considering that it has to account for PHP, the web server (apache, nginx, IIS etc) MySQL, MariaDB, Percona Server and others. Then you have to account for all the different cross versions and then try to port the schemas to a different set server with another set of versions, it gets complicated very quickly. With this in mind the plugin will probably always have room for improvement. This is why we have the community to rely on…

Sorry you spent so much time trying to work on things. If you ever want to revisit the issue feel free to submit a support ticket and I can try and see if I can get your package working on one of our servers…

Again thanks for the feedback!

Cheers~

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 guys…

I got the same error…
Taking a closer look I found this SQL generated by Duplicator to be responsible for creating the users table…

CREATE TABLE wp_users (
  ID bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  user_login varchar(60) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  user_pass varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  user_nicename varchar(50) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  user_email varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  user_url varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  user_registered datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  user_activation_key varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  user_status int(11) NOT NULL DEFAULT '0',
  display_name varchar(250) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  PRIMARY KEY (ID),
  KEY user_login_key (user_login),
  KEY user_nicename (user_nicename),
  KEY user_email (user_email)
) ENGINE=MyISAM AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

However trying to run it in phpmyadmin gave this error…
#1067 - Invalid default value for 'user_registered'

This seems to be the reason why table wp_users is not created…

Same thing seems to happen for wp_posts table…

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 there,

I totally AGREE with cbhurji on the issue regarding Live Site Transfer To LocalHost WAMP server.
The only solution I found for the problem (same as cbhurji faced and explained quite in detail for Live site—->Localhost WAMP server) is to manually copy the tables which get missing while the “installer.php ececution with Duplicator in action). The main tables which get missing (even shown in installer-log.txt) are wp_users and wp_posts tables and I tell you cbhurji, that its’s this reason that you get a SEMI-OK site on localhost as all posts get missing along with sitemap (if connected through google).

cbhurji, if you get any solution from the makers of duplicator, kindly share here.

thanks for reading my problem, appreciated!

Regards

I had wasted a lot of time on this problem.