Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi,

    I’ve found the reason for this to be new behavior in MySQL version 5.7 and higher

    Do you have Enable Brute Force Attack Prevention: enabled in the plugin under Brute Force?

    Thank you

    Thread Starter gsingh93

    (@gsingh93)

    No, it is not enabled. Why is that relevant?

    Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi,

    No, it is not enabled. Why is that relevant?

    No, I was just asking because of the following wp_clear_auth_cookie illustrated in your error message above.

    You might want to do a plugin/ theme conflict test. Just in case there is a conflict with one of your plugins or your theme.

    Regards

    • This reply was modified 4 years, 4 months ago by mbrsolution.
    zdrive

    (@zdrive)

    @gsingh93, I also had the errors in my log, but was able to fix the problem using your advice. Thanks for that! You’re correct, the value ‘1000-10-00 10:00:00’ is out of range. The lower limit for DATETIME in MySQL is ‘1000-01-01 00:00:00’. Correcting the value in ‘wp-security-user-login.php’ stopped the errors.

    However, because of the incorrect values in ‘wp-security-installer.php’ some database fields had default values of ‘0000-00-00 00:00:00’ in contradiction with the installer script. That’s because MySQL converts the incorrect date format to a “zero date” when strict mode is not enabled.

    So, I also changed the default values from ‘0000-00-00 00:00:00’ to ‘1000-10-10 10:00:00’ in these table.fields:
    wp_aiowps_failed_logins.failed_login_date
    wp_aiowps_login_activity.login_date
    wp_aiowps_login_activity.logout_date

    Thanks again!

    Plugin Contributor mbrsolution

    (@mbrsolution)

    Thank you for reporting this. I have submitted a message to the developers to investigate further this issue.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘WordPress database error Incorrect DATETIME value: ‘1000-10-00 10:00:00’ is closed to new replies.