MySQL 5.7 Compatibility

  • Resolved mumbomedia

    (@mumbomedia)


    4 years, 5 months ago

    The plugin isn’t 100% compatible with 5.7.

    If strict mode is enable, date values like 0000-00-00 00:00:00 are not allowed.
    This date value is default on wp_blc_synch column last_synch and in wp_blc_links for the columns first_failure, last_check, last_success, last_check_attempt.

    If this columns can also have no value I would recommend that they should be declared as nullable and the default value should be null.

    In the code it could be check with something like empty or == ”.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support Kris – WPMU DEV Support

    (@wpmudevsupport13)

    Hi @mumbomedia

    Thank you for all the additional data. I pinged our developers to take a closer look at this. We will post an update here as soon as we get information that will be available from them.

    Kind Regards,
    Kris

    Thread Starter mumbomedia

    (@mumbomedia)

    Your welcome

    That sounds good to me.

    Kind regards

    mumbomedia

    Plugin Support Patrick – WPMU DEV Support

    (@wpmudevsupport12)

    Hi @mumbomedia

    Could you please let us know if this not compatibility is causing a fatal error or only a warning?

    Best Regards
    Patrick Freitas

    Thread Starter mumbomedia

    (@mumbomedia)

    No problems arise in regular operation.
    Only when creating / importing a backup e.g. An error is thrown via PHPmyAdmin because the strict mode of MySQL 5.7 or higher does not allow invalid date values.
    You have to change the mode manually for the import to work via SET MODE=””.

    Since 5.7, such fields should be defined as nullable instead, which in my opion also makes more sense. From the PHP programming perspective, it shouldn’t make any difference whether you check against “0000-00-00 00:00:00” if the value is an empty string.

    Plugin Support Saurabh – WPMU DEV Support

    (@wpmudev-support7)

    Hello @mumbomedia,

    The Broken Link Checker team as made a note of the same and have lined up to fix the same in the future versions of the plugin. Also, I’m afraid I would not be able to give you an ETA on the same. You can keep an eye on the plugin updates so to know about the fix.

    I would also like to thank you for reporting this to us as this would help us in making it better. Should you have any questions or need any help, feel free to reply in the thread below or start afresh thread and we would be happy to help.

    Thank you,
    Prathamesh Palve

    Plugin Support Patrick – WPMU DEV Support

    (@wpmudevsupport12)

    Hi @mumbomedia

    I hope you are doing well.

    We haven’t heard from you in a while, I’ll go and mark this thread as resolved.

    As my friend told, we already reported this problem to the plugin developers, however, we can’t give an ETA.

    Feel free to let us know if you have any additional question or problem.

    Best Regards
    Patrick Freitas

    Thread Starter mumbomedia

    (@mumbomedia)

    Yeah that’s fine by me.

    I look forward to the next update.
    In the meantime, I’m going to ask our host if they can set the non-strict mode as the default so we won’t have any more problems doing a backup that we do by default every time we make major changes like wordpress- / plugin-updates or even a complete migration.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘MySQL 5.7 Compatibility’ is closed to new replies.