• Resolved fox-didl

    (@fox-didl)


    Just WooCommerce is active with thene storefront. Just fatal error – nothing else. Working on dev-site in staging. PHP 7.4 is working nice and ok for now, but it would be nice to be able to update to PHP 8.

    [08-May-2022 23:50:01 UTC] PHP Fatal error:  Uncaught ValueError: Missing format specifier at end of string in /www/htdocs/xxx/wp-content/plugins/woocommerce/includes/class-wc-post-types.php:232
    Stack trace:
    #0 /www/htdocs/xxx/wp-content/plugins/woocommerce/includes/class-wc-post-types.php(232): sprintf('Alle %', 'Anwendung')
    #1 /www/htdocs/xxx/wp-includes/class-wp-hook.php(307): WC_Post_Types::register_taxonomies('')
    #2 /www/htdocs/xxx/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters(NULL, Array)
    #3 /www/htdocs/xxx/wp-includes/plugin.php(474): WP_Hook->do_action(Array)
    #4 /www/htdocs/xxx/wp-settings.php(587): do_action('init')
    #5 /www/htdocs/xxx/wp-config.php(98): require_once('/www/htdocs/w00...')
    #6 /www/htdocs/xxx/wp-load.php(50): require_once('/www/htdocs/w00...')
    #7 /www/htdocs/xxx/wp-admin/admin.php(34): require_once('/www/htdocs/w00...')
    #8 /www/htdocs/xxx/wp-admin/plugins.php(10): require_once('/www/htdocs/w00...')
    #9 {main}
      thrown in /www/htdocs/xxx/wp-content/plugins/woocommerce/includes/class-wc-post-types.php on line 232
    • This topic was modified 2 years, 6 months ago by fox-didl.
Viewing 10 replies - 1 through 10 (of 10 total)
  • Hi @fox-didl

    Thanks for sharing the errors.

    PHP 8 is supported by WooCommerce running on a basic setup of the latest versions of WordPress, WooCommerce and the Storefront theme.

    I suspect that the issue you are facing could be due to inheritance errors. This documentation may be able to help you point in the right direction: https://developer.woocommerce.com/2020/10/30/developer-advisory-inheritance-in-php-8/

    If you require further help, please share a copy of your site’s System Status so we can take a more detailed look. You can find it via WooCommerce > Status. Select “Get system report” and then “Copy for support”. Once you’ve done that, paste it here in your response.

    Thanks

    Thread Starter fox-didl

    (@fox-didl)

    I think the problem could be that we are using mariaDB instead of MySQL. What do you think? I have no other idea.

    I can’t do what you need with status, because I can’t login anymore with PHP 8. Just “error” on Screen and Fatal Error in debug.log. Without WooCommerce plugin active, everything is fine. But with the try to activate WooCommerce, this fatal error is happening.

    • This reply was modified 2 years, 6 months ago by fox-didl.
    • This reply was modified 2 years, 6 months ago by fox-didl.

    Hi @fox-didl

    we are using mariaDB instead of MySQL

    As per our recommendations for the hosting environment, MySQL version 5.6 or greater OR MariaDB version 10.1 or greater is required.

    Here’s more information on our server requirements:
    https://woocommerce.com/document/server-requirements/.

    Since you are unable to go for the System Status Report, can you please confirm if your MariaDB version meets the minimum recommended requirement?

    Thread Starter fox-didl

    (@fox-didl)

    MariaDB 10.5.15 in usage.

    Thread Starter fox-didl

    (@fox-didl)

    Login is no problem with going back to PHP 7.4. But in this case there is no status report for you with php 8.

    Hi @fox-didl

    Login is no problem with going back to PHP 7.4

    Can you please log in, disable all plugins except WooCommerce, disable any/all custom code, and then upgrade to PHP 8?

    Do let us know of the outcome.

    Thanks

    Thread Starter fox-didl

    (@fox-didl)

    Sure. Changed to storefront and just WC active:
    https://ibb.co/DK4nfz1

    And now it’s working. How is this possible? This how-to-update isn’t a nice working solution. Any idea to do this in a better way?

    Hi @fox-didl

    Glad to know that it is finally working! ??

    Yes, of course, that isn’t the best way to do that. It seems that there was something that posed a compatibility issue.

    Cheers

    Thread Starter fox-didl

    (@fox-didl)

    Will test more now. Thanks a lot and I think you should inform your customers about this workaround by updating on PHP 8. Newsletter?

    Hi @fox-didl

    You’re welcome!

    That’s a good idea!

    Please feel free to create a new topic if you have other questions.

    Thanks

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Still no PHP 8 support’ is closed to new replies.