wp_users not being created

Hey @aum001,

Can you check the installer-log.txt and see if you see any errors in the log file?

Thanks~

I run into the same problem with XAMPP but the DB uses a strict mode which prevents tables to be created. See as well
https://stackoverflow.com/questions/36374335/error-in-mysql-when-setting-default-value-for-date-or-datetime

Hi Maria,

On step 2 of the installer under options you can adjust the Mode, in most cases if you enter in “NO_ENGINE_SUBSTITUTION” it should work.

https://dev.mysql.com/doc/refman/5.7/en/sql-mode.html#sqlmode_no_engine_substitution

Let me know if that helps~

Hi Cory,

thx for the update – which works. BUT as a general remark I would prefer to see a short note that not all tables could be restored… Namely the wp_users is NOT listed although it is in the create statement and the log-files show an error.

I would like to see some kind of Error message that some tables are skipped – see log file. AND than leave the user the chance to either import despite missing tables OR give a hint that this might be solved with the sql-mode-subtitution…

My 2 cents….

Hey @maria_wp,

On step 4 of the installer there is a report section that should have shown that you had errors. Did that section not show up for you?

Thanks~

hi Cory,

yeah, on step 4 the report sections mentions the error. But I have to confess that stepping from step3 to step4 I would assume that everything works fine and step3 finished gracefully. And errors can only occur when stepping from step3 to step4.

Matter of fact is that step3 already has errors (not all tables were generated) AND I have no clue about it (when I stay in step3). Yeah, in step4 I get information finally – but this forces me to rethink that on step3 severe errors have been occurred and the code nevertheless continued.

as mentioned above – I personally would have liked to see an error-msg before hand. Anyway – issue is currently resolved – cuz I figured out the problem. Just as some kind of feedback from the expectation-side ??

Sounds Good! We’ll see if there is an effective way to make the issue more visible in a future release…

Cheers~