• Resolved steckscout

    (@steckscout)


    Hello! A few days ago I received an automated email from my website notifying me that there has been a fatal error related to Forminator with this message:

    An error of type E_ERROR was caused in line 800 of the file
    /srv/htdocs/wp-content/plugins/forminator/library/class-export.php.
    Error message: Maximum execution time of 1200 seconds exceeded

    Here is some basic information about my site:
    WordPress version 5.5.3
    Current theme: Collective (version 1.1)
    Current plugin: Forminator (version 1.14.6)
    PHP version 7.4.13

    Despite receiving this message everything seems to be working as expected. Should I be worried? What steps can I take to resolve this? What problems would one expect to see from this error message? Thank you!

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Support Patrick – WPMU DEV Support

    (@wpmudevsupport12)

    Hi @steckscout

    Sorry to hear you had this issue.

    Could you check your WordPress memory limit, PHP limit and Max Execution Time?

    If those values are too low it can cause this problem.

    You can increase the memory limit following this guide:
    https://premium.wpmudev.org/blog/increase-memory-limit/

    Let us know the result you got.
    Best Regards
    Patrick Freitas

    Thread Starter steckscout

    (@steckscout)

    @wpmudevsupport12

    I spoke with a WordPress Happiness Engineer who informed me that all of those values are controlled on their end and I cannot do anything to modify those values.

    Plugin Support Amin – WPMU DEV Support

    (@wpmudev-support2)

    Hello @steckscout ,

    Are you still experiencing this issue? I mean are you still receiving those emails with errors?
    That could be a one-time thing, but when it happens often I would suggest first re-installing plugin (make sure that in Forminator -> Settings -> Data you selected Preserve).
    If that would not help, then the next step would be to run a plugin conflict test https://premium.wpmudev.org/blog/wordpress-plugin-conflicts-how-to-check-for-them-and-what-to-do/

    kind regards,
    Kasia

    Thread Starter steckscout

    (@steckscout)

    @wpmudev-support2

    I went ahead and uninstalled and re-installed the plugin, this seems to have improved some other minor issues I was having, but the error message has persisted. Would a delay between the re-installation of the plugin and the disappearance of the error be possible?

    Also, I followed along in the article you provided about detecting plugin conflicts, the article isn’t entirely applicable to the situation I’m currently in because everything does seem to be working entirely fine (aside from the occasional instance where forms simply just don’t load and instead leave blank rectangles) so it’s hard to identify any particular cause to the error.

    Hi @steckscout,

    Can you try going to Forminator > Submissions panel, click on Export button in top right corner and if you have scheduled exports enabled try disabling them and see if the error stops showing up after that?

    Cheers,
    Predrag

    Thread Starter steckscout

    (@steckscout)

    @wpmudev-support1

    I do have exports enabled on a limited number of forms, but for those that have it enabled at this point in time it’s a necessity

    Hi @steckscout,

    Does the time of the error in the email correspond with the time of the exports that are scheduled?

    Are the scheduled times during high site traffic times by any chance?

    Cheers,
    Predrag

    Thread Starter steckscout

    (@steckscout)

    @wpmudev-support1

    The exports are at relatively low traffic times, and of six error emails not one of them happens within an hour in either direction of the exports. The exports we do use are very limited, one hasn’t happened for a few weeks and even when we do there’s at most three exports happening in one day, usually less. Though the traffic of exports should be increasing in early January.

    Plugin Support Amin – WPMU DEV Support

    (@wpmudev-support2)

    Hello @steckscout ,

    Can you enable debug log in the WordPress (https://premium.wpmudev.org/blog/debugging-wordpress-how-to-use-wp_debug/ ) and share with us it after those errors will occur. Maybe there are other related warnings that will point us to the right direction.

    kind regards,
    Kasia

    Thread Starter steckscout

    (@steckscout)

    @wpmudev-support2

    I went ahead and enabled the debug log, I’m no longer seeing the maximum execution time error. Is this something that can come and go on a regular basis if it’s known to be an issue or is it more consistent?

    Plugin Support Nithin – WPMU DEV Support

    (@wpmudevsupport11)

    Hi @steckscout,

    Is this something that can come and go on a regular basis if it’s known to be an issue or is it more consistent?

    When you enable the debug mode the related errors will be saved inside a file called debug.log, under /wp-content directory and the error won’t appear in the frontend so maybe that’s what you are noticing. Please share the debug.log file in the next response as mentioned in our previous reply so that we could investigate the logs further.

    I’m afraid we cannot comment the reason on what causes this as it’s something we couldn’t replicate on our side, so it’s tough to say what exactly is causing this at the moment.

    Please do get back with the debug.log file. Looking forward to your response.

    Regards,
    Nithin

    Plugin Support Amin – WPMU DEV Support

    (@wpmudev-support2)

    Hello @steckscout ,

    We haven’t heard from you for a while now – looks like you no longer need our assistance.

    Please feel free to re-open this ticket if needed.

    kind regards,
    Kasia

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Maximum Execution Time Fatal Error’ is closed to new replies.