Fatal Error v4.0.8

  • Resolved WPdev2022

    (@ernestph)


    1 year, 12 months ago

    Latest version is not yet compatible with the latest WordPress core. I think that’s where the issue is. Additionally, WooCommerce is activated and it’s the latest version 7.5.1. Thanks!

    Error message: Uncaught Error: Call to protected method class@anonymous::deleteCache() from context ‘TheFrosty\WpUtilities\WpAdmin\DashboardWidget’ in /home/garden-house-flags/webapps/garden-house-flags/wp-content/plugins/custom-login/vendor/thefrosty/wp-utilities/views/dashboard-widget/rest.php:15
    Stack trace: #0 /home/garden-house-flags/webapps/garden-house-flags/wp-content/plugins/custom-login/vendor/thefrosty/wp-utilities/views/dashboard-widget.php(26): include() #1 /home/garden-house-flags/webapps/garden-house-flags/wp-content/plugins/custom-login/vendor/thefrosty/wp-utilities/src/WpAdmin/DashboardWidget.php(72): include(‘/home/garden-ho…’) #2 /home/garden-house-flags/webapps/garden-house-flags/wp-admin/includes/template.php(1409): TheFrosty\WpUtilities\WpAdmin\DashboardWidget->TheFrosty\WpUtilities\WpAdmin{closure}() #3 /home/garden-house-flags/webapps/garden-house-flags/wp-admin/includes/dashboard.php(271): do_meta_boxes() #4 /home/garden-house-flags/webapps/garden-house-flags/wp-admin/index.php(203): wp_dashboard

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author Austin

    (@austyfrosty)

    What versions of PHP and WordPress are you on?

    Thread Starter WPdev2022

    (@ernestph)

    WordPress is Current version: 6.1.1
    While PHP is still 7.4.33 (Supports 64bit values)

    Plugin Author Austin

    (@austyfrosty)

    Thanks for the report. It’s not a FATAL Error, just an Uncaught Error. It’s an edge case notice that will likely not be triggered often.

    That being said, I’ll see about getting a fix in as soon as I can.

    Howdy people.

    I am getting exactly the same error than @ernestph very often. If it occurs once, this is going to continue throwing always, unless making public the $wpRemote->retrieveBodyCached method and removing $wpRemote->getQueryCacheKey(), which throws a error due to not initialized property.

    My site runs in PHP 7.4. It does not seem a conflict with another plugin.

    @austyfrosty You can see reproduce the error in wp-admin/options-general.php?page=custom-login ang get the screen:

    Plugin Author Austin

    (@austyfrosty)

    I have a fix in place already, but it needs to be back ported for PHP < 8.0 support which I haven’t had the time to execute yet. I am hoping I can in the next week or two.

    Thread Starter WPdev2022

    (@ernestph)

    @austyfrosty Just want to inform you that I tested PHP 8.0 in a staging site and the uncaught error was still there… Making the plugin not usable.

    https://share.getcloudapp.com/jkuAE1X7

    Plugin Author Austin

    (@austyfrosty)

    @wpdev2022 I didn’t say it was resolved for PHP 8.0+, rather in an upstream package the underlying issue was resolved but required PHP >= 8.0. So I was unable to update Custom Login with the dependency.

    Regardless, I have back ported the fix and pushed Custom Login 4.0.9.

    This will likely be the last PHP 7.4 release, as I no longer with with PHP less than 8.0.

    • This reply was modified 1 year, 11 months ago by Austin.
    Plugin Author Austin

    (@austyfrosty)

    This will likely be the last PHP 7.4 release, as I no longer working with PHP less than 8.0.

    Hi @austyfrosty . Unfortunatly, my site got another fatal error. The fix change the original fatal for another not fixed syntax.

    PHP Fatal error:  Uncaught Error: Typed property class@anonymous::$queryCacheKey must not be accessed before initialization in /wp-content/plugins/custom-login/vendor/thefrosty/wp-utilities/src/Api/WpCacheTrait.p
hp:37

    I don’t think the fatals errors are due to PHP version. About this fatal error: https://deepsource.io/directory/analyzers/php/issues/PHP-E1008.

    I fixed this last bug on my site and for now it has not crashed the config page.

    Thread Starter WPdev2022

    (@ernestph)

    That is correct. New version is still having a critical error…

    I have same issue – Following

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Fatal Error v4.0.8’ is closed to new replies.

Tags