Are you a GenerateCustomer?

Do you have an active GP Premium or GenerateBlocks Pro license key?

Create a GenerateSupport account for GeneratePress and GenerateBlocks support in one dedicated place.

Create an account
Already have a GenerateSupport account? Login

Just browsing?

Feel free to browse the forums. Support for our free versions is provided on WordPress.org (GeneratePress, GenerateBlocks).

Want to become a premium user? Learn more below.

Critical error after PHP 8.2 Upgrade

  • Hello,
    I use GP for everything and haven’t had a problem with other PHP 8.2 upgrades (from 7.4)

    This one created the white screen critical error message. If all plugins are deactivated, the error still happens unless the default theme is selected. The site works with the default theme and all plugins activated.

    I have included the log from the host in the private info as well as an Admin login.

  • Hi there,

    My GP site is running 8.2.10, it has no issues.

    The error log didn’t mention GP once, so I don’t think it’s a GP issue.

    If all plugins are deactivated, the error still happens unless the default theme is selected.

    Are you referring default theme to the GP parent theme? If so, the issue is from your child theme, disable all your custom functions and see if the issue gets fixed.

  • Sorry, I meant twentytwentyfour – when using that it works.

  • Does using GP parent theme work?

  • When I try to activate the parent theme on the staging website, which is still on PHP 7.4, I get the same error screen

    There has been a critical error on this website. Please check your site admin email inbox for instructions.

    For the other error messages I had not received an email but I did get one this time.
    An error of type E_ERROR was caused in line 525 of the file /www/wp-content/plugins/megamenu/classes/style-manager.class.php. Error message: Allowed memory size of 134217728 bytes exhausted (tried to allocate 962560 bytes)

    Edited – I was able to upgrade to PHP 8.2 when I had default GP and no MMM. When I opened the admin side, it worked til I selected my child theme of GP and that threw the error again.

  • Edited – I was able to upgrade to PHP 8.2 when I had default GP and no MMM. When I opened the admin side, it worked til I selected my child theme of GP and that threw the error again.

    So it’s confirmed that the issue is in your child theme. Try to disable all your custom functions and see if the issue gets fixed.

  • I just figured it out – there was some code in the functions.php referencing Max Mega Menu and once I deleted that it worked fine. Thanks!

  • Glad to hear that 🙂

Viewing 8 posts - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.