• Resolved pgpagely

    (@pgpagely)


    There seems to be an issue with the migration part of the new 3.0.0 updated. We are seeing this issue across many sites and servers.

    When the update happens, it is calling:

    PrliUtils->migrate_after_db_upgrade()

    This then calls:

    $cpt_id = $prli_link->create_cpt_for_link($link->name, $link->created_at, $link->updated_at);

    The problem is that at least in our examples, every entry in the wp_prli_links table has an updated_at value of NULL. The create_cpt_for_link function then tries to do a direct insert to the wp_posts table except the values for post_modified and post_modified_gmt respectively come out like so:

    NULL, '1970-01-01 00:00:00'

    This is not allowed by the wp_posts table schema:

    WordPress database error Column 'post_modified' cannot be null for query...

    This causes a lot of spam in error logs (in fact we’ve seen it creating 10+GB of error logs quite easily) and also causes load on the database. It then seems to keep trying every 30 minutes due to the transient you have to retry installations.

    A fix for this problem ASAP would be very useful.

Viewing 11 replies - 1 through 11 (of 11 total)
  • Having the same issue. Never had problems with Pretty Link before but since the new update it has crashed our site and thrown gigs worth of errors in the logs, same messages as above. Have had to roll back to 2.1.8 since that’s the last backup we have that includes the pro folder.

    Note: disabling the plugin and rolling it back didn’t immediately fix the problem or stop whatever processes were causing the error. It continued for another 20 minutes even after uninstalling 3.0 and reinstalling 2.1.8

    Thread Starter pgpagely

    (@pgpagely)

    Note: disabling the plugin and rolling it back didn’t immediately fix the problem or stop whatever processes were causing the error. It continued for another 20 minutes even after uninstalling 3.0 and reinstalling 2.1.8

    We saw the same behaviour, a restart of PHP was required to fully fix the issue.

    The issue is quite bad. All of the following symptoms are present:
    – Significantly increased storage usage due to logging the whole query
    – Increased memory usage, the tasks seem to go on for more than 30 minutes due to the rows never being processed, and I believe end up stacking
    – Increase CPU usage for same reasons as above
    – Increased load on database as it is hammered with bad queries

    Plugin Author cartpauj

    (@cartpauj)

    We are working on an update to address this issue. Thanks for the detailed feedback!

    Same issue here over 36GB of error logs deleted.

    Plugin Author cartpauj

    (@cartpauj)

    We are working on a fix for this issue. Very sorry for the troubles! It would probably be best for anyone affected by this to downgrade back to the prior version ( https://downloads.wordpress.org/plugin/pretty-link.2.1.10.zip ) until we release 3.0.1

    Just found this issue. Affecting me bad.
    I deleted the plugin for now but it is still filling my log files with these exact errors

    Plugin Author cartpauj

    (@cartpauj)

    @edholtzman sorry for the troubles! It’s probably best to downgrade until we get 3.0.1 out.

    https://downloads.wordpress.org/plugin/pretty-link.2.1.10.zip

    Hi,

    when you thinking you are going to release 3.0.1 as this is pretty bad? Also, when you downgrade are the links saved going to disappear?

    Thanks

    Thread Starter pgpagely

    (@pgpagely)

    when you thinking you are going to release 3.0.1 as this is pretty bad?

    About 9 hours ago by the looks of it.

    Hey pgpagely,
    Have you updated to new version yet? Hesitant to update until we know that the issue has actually been resolved. Was wondering if you’ve given it a shot yet?
    Thank you!

    Thread Starter pgpagely

    (@pgpagely)

    Hey pgpagely,
    Have you updated to new version yet? Hesitant to update until we know that the issue has actually been resolved. Was wondering if you’ve given it a shot yet?
    Thank you!

    Checked the code before updating and yes we did do it. Can’t speak for any of the other issues people have reported with 3.0.0 but it fixes this particular problem by defaulting to the current time if it detects the value is NULL.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘NULL values in database queries’ is closed to new replies.