• Resolved thartl

    (@hartl)


    I am seeing fatal errors after update to 3.0.1

    PHP Fatal error: Composer detected issues in your platform: Your Composer dependencies require a PHP version “>= 8.1.0”. You are running 8.0.30. in …/files/wp-content/plugins/genesis-blocks/vendor/composer/platform_check.php on line 24

    Updating to PHP 8.1 resolves the issue, but we have some sites that need to stay on PHP 8.0 for the time being.

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Contributor Ryan Kienstra

    (@ryankienstra)

    Hi @tharti,

    Sorry, that’s a pain to see a PHP fatal error, and to have no way to fix it without updating to PHP 8.1.

    Would you be OK with waiting until you can run PHP 8.1 to update Genesis Blocks to the latest (3.0.1), and staying on Genesis Blocks 3.0.0 for now?

    The only thing we did in the 3.0.1 release is bump the required PHP version to8.1.

    • This reply was modified 11 months, 2 weeks ago by Ryan Kienstra.
    Thread Starter thartl

    (@hartl)

    Hi @ryankienstra,

    Yes, we can do that. It’s an extra push to upgrade some sites, and that’s okay.

    I am also realizing that manual updates from the back end are disabled for the wrong PHP versions.

    Remote / automated plugin updates by wpmudev don’t seem to respect the php requirements, whereas e.g. managewp do. Hence the fatal errors. I will mentiont it to them.

    Thank you for the quick reply.

    I can report the same issue.

    Ours is caused by using Composer/Wpackagist to manage updates.

    Could I suggest that you release(d) a version that notify the user/admin of the impending bump, before making the change?
    I can understand that >8.1 will be End of Life shortly. However we do still have a few weeks to finish off upgrading.

    Plugin Contributor Ryan Kienstra

    (@ryankienstra)

    Thanks, @hartl. Sorry for the pain of the fatal error and asking you to wait.

    Plugin Contributor Ryan Kienstra

    (@ryankienstra)

    Hi @michaelbragg,

    Thanks for letting me know about this, and sorry for the hassle of not being able to upgrade and maybe a fatal error.

    Could I suggest that you release(d) a version that notify the user/admin of the impending bump, before making the change

    Good idea, that would have made this less painful.

    Is your site going to be OK waiting until you can update to PHP 8.1 before updating Genesis Blocks to the latest?

    • This reply was modified 11 months, 2 weeks ago by Ryan Kienstra.
    • This reply was modified 11 months, 2 weeks ago by Ryan Kienstra.

    Is your site going to be OK waiting until you can update to PHP 8.1 before updating Genesis Blocks to the latest?

    It should be thank you. The Upgrade to PHP 8.2 is imminent.
    Rolling back to 3.0.0 resolved the issue. We’ve fixed it at that version for the short term.

    Thanks @ryankienstr

    Plugin Contributor Ryan Kienstra

    (@ryankienstra)

    Thanks for your patience, @michaelbragg. Good to know your site is in good shape.

    I can report the same issue. I came here to see what solutions are being offered. Upgrading to 8.1 broke sites using some of the older Genesis themes. So I rolled back the PHP back to 7.4 and then Genesis Blocks to 3.0. Also, imo, requiring a different version of PHP is a major revision, not a minor revision.

    Plugin Contributor Ryan Kienstra

    (@ryankienstra)

    Also, imo, requiring a different version of PHP is a major revision, not a minor revision.

    Thanks, that’s a good point.

    We just changed the required PHP version back to 7.1. in Genesis Blocks 3.1.0.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Fatal errors after update to 3.0.1’ is closed to new replies.