Workaround for Fatal Error when updating from 4.39.0

  • Resolved ektagon

    (@ektagon)


    11 months, 2 weeks ago

    Just notified MailPoet about this, but wanted to share here too for any sites who can’t update any plugins (via WordPress Updates page) due to this bug.

    In short, in some versions of PHP (8+) a fatal error related to using object of stdClass as array blocks the page from fully loading. This blocks sites from being able to update any plugins or themes via this interface.

    This seems to be caused by a bug in 4.39.0 of MailPoet Premium. Updating to 4.40.0 fixes this.

    The workaround is to update to MailPoet Premium 4.40.0 from the Plugins list (/wp-admin/plugins.php). Doing so ‘fixes’ the WordPress Updates page.

    Hope this helps someone avoid stress/panic/etc.

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

  • I was trying to figure this out! Thank you for confirming! This is also occurring on websites running on PHP 7.4.

    Plugin Support Dani F. a11n

    (@danielinhou)

    Hi @ektagon ????,

    Thanks for publishing the advice. I can confirm that we have reported the issue to the MailPoet developers and also that updating to 4.40.0 fixes it.

    I am marking the topic as resolved now.

    Cheers

    Thread Starter ektagon

    (@ektagon)

    Hey @danielinhou this issue is back with the update from 4.40.0 to 4.41.0

    On plugin update page (/wp-admin/update-core.php) there’s this error:

    Fatal error: Uncaught Error: Cannot use object of type stdClass as array in /home/x/public_html/wp-admin/update-core.php:520 Stack trace: #0 /home/x/public_html/wp-admin/update-core.php(1118): list_plugin_updates() #1 {main} thrown in /home/x/public_html/wp-admin/update-core.php on line 520

    And page breaks just under MailPoet item in table.

    Updating MailPet (core plugin, not Premium) via /wp-admin/plugins.php fixes this issue.

    Plugin Support Feten L. a11n

    (@fetenlakhal)

    Hi there!

    Thank you for sharing this. I will let the developers know!

    Let us know if you’ll have any further questions!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Workaround for Fatal Error when updating from 4.39.0’ is closed to new replies.