Support » Plugin: WooCommerce » PHP Fatal error

PHP Fatal error

  • Resolved cfm168

    (@cfm168)


    5 months, 3 weeks ago

    Hello,

    I am running with WP6.2, PHP8.1 and WC version 7.6.0.

    This is my first time getting the following error after upgrading to WC v7.6.0.

    Here are the last 1 entries from /home/SorryHided/php-errors.log:

    [Apr 15, 14:15:08] PHP Fatal error: Uncaught TypeError: Unsupported operand types: float + string in /home/SorryHided/SorryHided.com/wp-content/plugins/woocommerce/includes/abstracts/abstract-wc-order.php:1920
    Stack trace:
    WC_Abstract_Order->calculate_totals(false) /home/SorryHided/SorryHided.com/wp-content/plugins/woocommerce/includes/class-wc-ajax.php:1096
    WC_AJAX::add_order_fee(”) /home/SorryHided/SorryHided.com/wp-includes/class-wp-hook.php:308
    WP_Hook->apply_filters(”, Array) /home/SorryHided/SorryHided.com/wp-includes/class-wp-hook.php:332
    WP_Hook->do_action(Array) /home/SorryHided/SorryHided.com/wp-includes/plugin.php:517
    do_action(‘wp_ajax_woocomm…’) /home/SorryHided/SorryHided.com/wp-admin/admin-ajax.php:188
    {main}
    thrown in /home/SorryHided/SorryHided.com/wp-content/plugins/woocommerce/includes/abstracts/abstract-wc-order.php on line 1920

    Please help to fix this issue. Thanks in advance!

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Shameem (woo-hc)

    (@shameemreza)

    5 months, 2 weeks ago

    Hi @cfm168

    Based on the error message you’ve provided, there seems to be a type mismatch issue in the abstract-wc-order.php file, specifically on line 1920. An unsupported operation between a float and a string causes the error. To fix this issue, I would recommend the following steps:

    1. First, ensure that all your plugins and themes are up-to-date, as outdated plugins or themes may cause compatibility issues with the latest version of WooCommerce. If you have any custom code in your theme or plugins, ensure they handle data types correctly.

    2. If the issue persists, temporarily deactivate all non-WooCommerce plugins and switch to a default Storefront theme. This will help determine if there’s a conflict with another plugin or your theme. If the issue is resolved after deactivating the plugins and switching the theme, you can reactivate them individually to find the conflicting plugin or theme.

    3. If the issue still persists, you may need to roll back to a previous version of WooCommerce while WooCommerce investigates this issue further. You can use the WP Rollback plugin to revert to an earlier version. Please make sure to create a full backup of your site before rolling back.

    If you have followed these steps and are still experiencing issues, please share your System Status Report, which you can find via WooCommerce > Status. Select Get system report and then Copy for support. Once you’ve done that, paste it into your reply here. This will help the team investigate further and provide you with a more accurate solution.

    Thread Starter cfm168

    (@cfm168)

    5 months, 2 weeks ago

    @shameemreza – Thank you for prompt response. After conflict check by Health Check & Troubleshooting plugin, so far found Woocommerce child in my twentyeleven child theme seems needed to be updated. Woocommerce-child developed by Ray Ho (the name as author) who is one of Code Wrangler @automattic, but I can’t reach him. I really not sure if the error caused by the child theme. But I want to contact Ray Ho to update the child for Woocommerce first. Hope you can help. Thanks in advance.

    xue28 (woo-hc)

    (@xue28)

    5 months, 2 weeks ago

    HI @cfm168

    Thanks for reaching out!

    I understand that you received the error message above after updating WooCommerce to version 7.6.0, correct?

    Furthermore, after performing the full conflict test as suggested above, you found out that the issue is coming from your child theme, correct?

    I’d like to understand your site properly. Please share your System Status Report that you can find via WooCommerce > Status. Select Get system report and then Copy for support. Once you’ve done that, you can paste it into your reply here.

    You could copy and paste your reply here or paste it via https://gist.github.com/ and send the link here.

    Thanks!

    Thread Starter cfm168

    (@cfm168)

    4 months, 3 weeks ago

    Hi @xue28 – Thank you for helping. Yes, I believe I found out that the issue is coming from child theme. Hope you can help. I will provide the system report via github later.

    Thanks in advance!

    xue28 (woo-hc)

    (@xue28)

    4 months, 3 weeks ago

    Hi @cfm168

    You are most welcome and we’re glad that worked! 🙂

    Please copy and paste the requested information here for us to check this further.

    Thanks!

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

Views