Database errors in 5.14.0

  • Resolved gutding

    (@gutding)


    9 months, 1 week ago

    Hello,

    I’m writing to report several recurring errors that appeared in my WordPress error log after upgrading to MailPoet version 5.14.0. The issues ceased immediately after I reverted back to version 5.13.2.

    The error log indicates a few different types of problems:

    • Database Lock wait timeout errors: The most frequent errors are Lock wait timeout exceeded; try restarting transaction. These occur when MailPoet attempts to delete old log entries from the wp_mailpoet_log table. This suggests a possible conflict with other database processes or that the query in this new version is taking too long to complete.
    • File access failures: The logs show critical PHP errors like Failed opening required... and Failed to open stream. It appears the plugin is unable to find and load specific PHP files, such as class-personalization-tag.php and class-html2text.php.
    • Missing Class Fatal error: The plugin crashes with a Fatal error: Uncaught Error: Class "MailPoet\Config\Capabilities" not found. This happens during the init action, indicating an issue with how the new version initializes its components.

    These errors seem to point to a combination of database optimization issues and problems with the file structure in version 5.14.0. Since reverting to version 5.13.2 resolved all the issues, it seems to be a regression introduced in the latest update.

    You can find a copy of the error log for your reference here.

    Thank you for your assistance.

Viewing 1 replies (of 1 total)
  • Plugin Support Gui A. a11n

    (@guicmazeredo)

    9 months, 1 week ago

    Hi there,

    Thanks for reporting this issue.

    We recently encountered a few similar cases like yours of site slowness that actually turned out to be caused by huge numbers of log entries in the database, and timeouts when the site tries to clear them out.

    As a workaround, we discovered that changing the “Logging” setting to Errors only in MailPoet > Settings > Advanced should fix the issue. 

    Our devs are already working on a fix that should be included on our next release with an ETA on next Tuesday, 9th. After the update, you should no longer experience this issue, even if you have logs set to Everything. 

    If you’d like to clear the extra logging details caused by this issue in your database, you can remove older entries from the wp_mailpoet_log table. The SQL query below should work to delete logs older than a month.

    DELETE FROM wp_mailpoet_log WHERE created_at < '2025-08-03 14:24:03' ORDER BY id ASC LIMIT 1000

    Please, make sure to create a backup of your website before running this query. 

    If you have any questions, let us know!

Viewing 1 replies (of 1 total)

The topic ‘Database errors in 5.14.0’ is closed to new replies.