new built-in feature to detect fatal errors

  • A few of my customers have been receiving these messages from WordPress. In all cases I have not found anything visibly wrong on the sites – no error messages and functionality seems to be fine. How should these be addressed? Do we ignore them? Post them to support for each plugin developer or here? In all instances the customer is using the same hosting company, and versions of PHP, MySQL, etc., are all current, as are the plugins, with no alerts to update anything.

    Pasted below is the content of 3 such messages, the first one containing the entire top portion of the emails with personal data removed. Thanks for any tips.

    Howdy!

    Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

    In this case, WordPress caught an error with one of your plugins, FooBox Image Lightbox.

    First, visit your website (URL here) and check for any visible issues. Next, visit the page where the error was caught (domainname.com/wp-login.php) and check for any visible issues.

    Please contact your host for assistance with investigating this issue further.

    If your site appears broken and you can’t access your dashboard normally, WordPress now has a special “recovery mode”. This lets you safely login to your dashboard and investigate further.

    (URL here)

    To keep your site safe, this link will expire in 1 day. Don’t worry about that, though: a new link will be emailed to you if the error occurs again after it expires.

    Error Details
    =============
    An error of type E_ERROR was caused in line 20 of the file /home/name/public_html/wp-content/plugins/woocommerce/includes/wc-core-functions.php. Error message: Out of memory (allocated 10485760) (tried to allocate 65536 bytes)

    Error Details
    =============
    An error of type E_ERROR was caused in line 49 of the file /home/name/public_html/wp-content/plugins/foobox-image-lightbox/freemius/require.php. Error message: Out of memory (allocated 10485760) (tried to allocate 126976 bytes)

    Error Details
    =============
    An error of type E_ERROR was caused in line 3648 of the file
    /home/name/public_html/wp-content/plugins/backupbuddy/classes/core.php.
    Error message: Maximum execution time of 30 seconds exceeded

Viewing 3 replies - 1 through 3 (of 3 total)

  • How should these be addressed? Do we ignore them?

    These errors were happening before, but you didn’t know. So I suppose you could continue to ignore them. But you could also fix them. The ones that run out of memory might need a larger memory allocation, especially for a store where you don’t want to interrupt the flow of a transaction.
    And for the last one where the backup is not completing, it wouldn’t do you any good to have a partial backup when you really need a complete backup.
    You can ask at each plugin’s support forum for how to deal with the error encountered.

    Thread Starter hollykny

    (@hollykny)

    The memory issues are confusing. For the sites where I’ve received these warnings, we’ve never seen a crash, white screen, complaint from a customer, etc. that a lightbox won’t open and such. But we could definitely look into increasing memory with the hosting company. I’ve posted these on each plugin’s forum as well. Thanks for your input, Joy.

    I know this thread is old, but if anyone else encounters a similar issue with BackupBuddy and exceeding the max execution time, BackupBuddy has an option to try and help with that located here in the plugin’s settings:
    BackupBuddy -> Settings -> Advanced Settings/Troubleshooting -> Basic Operation -> Attempt to override PHP max execution time ->
    Just check that, then save settings and try again.

    However most hosts don’t allow a PHP script to override server settings like that. So you may wish to contact your host so you can adjust/increase it at the server level.
    https://ithemes.com/custom_php_ini/

    • This reply was modified 5 years, 6 months ago by Andrew Nevins.
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘new built-in feature to detect fatal errors’ is closed to new replies.