• Resolved mbaccarella

    (@mbaccarella)


    Plugin update 5.12.5 crashes my WordPress site. I tested it and am now certain that it is the plugin that causes the problem. If I update to the new version, I get a fatal error that corrupts code on the page wp-includes/wp-db.php. I reinstalled a backup version of the site to restore it, but when I tried again to reinstall the plugin update, it crashed again. If I leave the plugin at version 5.11.5, it works correctly.

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Contributor webnus

    (@webnus)

    Hi @mbaccarella,

    Regarding the “fatal error” can you please follow the steps explained in this article: https://webnus.net/dox/modern-events-calendar/what-to-do-if-i-see-fatal-error/.

    Please keep us posted.

    Best Regards

    Hello,

    I can confirm that it is definitely an issue with MEC as my website is also suffering from the same issues. I have debugged and put it down to MEC and this function in wordpress ob_end_flush()

    If i uninstall MEC then all my problems go away, my site suffers 500 errors on any page MEC is used.

    Plugin Contributor webnus

    (@webnus)

    Hi @jiberson,

    Please make sure using the correct configuration for your server (especially PHP):
    https://ww.wp.xz.cn/about/requirements/

    Regarding the “ob_end_flush() function error”, please send a screenshot form the error, so we will be forwarded this topic to the developer team and it will be fixed for the next updates.

    Best Regards

    I have no issues with my PHP configuration. I also have no issue if I disable MEC, but on enabling every page I try to access the uses it comes back with this error.
    Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 172032 bytes) in /var/www/vhosts/clubalfa.co.uk/httpdocs/wp-includes/functions.php on line 4669

    This points to “ob_end_flush()” in these files.

    Thread Starter mbaccarella

    (@mbaccarella)

    I agree with jiberson, and I get the exact same fatal error. Also, I would not label my comment “resolved”, but rather responded to.

    I have now rolled back to 5.12.0 and all issues resolved.

    Plugin Contributor webnus

    (@webnus)

    Hi all,

    Alright, this issue is forwarded to the developer team, it will be checked and we will let you know the result.

    I appreciate your patience.

    Best Regards

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

The topic ‘Plugin update 5.12.5’ is closed to new replies.