• Resolved cfm168

    (@cfm168)


    Just updated to WC9.8.5 and got the following errors:

    Fatal error: Uncaught Error: Class “WC_Log_Levels” not found in /home/SorryHidedmysite/SorryHidedmysite.com/wp-content/plugins/woocommerce/includes/class-wc-logger.php:236

    Stack Trace


    1. WC_Logger->critical(‘Uncaught Error:…’, Array)
      /home/SorryHidedmysite/SorryHidedmysite.com/wp-content/plugins/woocommerce/includes/class-woocommerce.php:415

    2. WooCommerce->log_errors()

    3. {main}
      thrown in /home/SorryHidedmysite/SorryHidedmysite.com/wp-content/plugins/woocommerce/includes/class-wc-logger.php on line 236

    I’m running on WP6.8.1. This is first time happened with the error. Please advise what’s wrong. Thanks in advance!

Viewing 15 replies - 1 through 15 (of 16 total)
  • Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi there!

    Thank you for sharing the detailed error message following your update to WooCommerce 9.8.5. I understand how encountering a fatal error like this can be concerning, especially when it’s the first time you’ve seen it.

    The error “Class ‘WC_Log_Levels’ not found” usually indicates that some WooCommerce files may not have been fully updated or loaded correctly. This can sometimes occur if the update process was interrupted or if there is a caching issue.

    To troubleshoot further, if you are using any caching plugin, could you please try clearing your site cache? After that head over to WooCommerce → Status → Tools, and do the following:

    • WooCommerce transients – Clear
    • Expired transients – Clear
    • Clear template cache – Clear
    • Capabilities – Reset Capabilities
    • Clear customer sessions -Clear

    IF you still face the same issue, could you please create a staging site? You can use the following plugin to do so:https://wordpress.org/plugins/wp-staging/

    Once you create the staging site, please try reinstalling WooCommerce and see if that works for you.

    In the meantime, I’d like to understand your site properly. Please share with us the necessary information below for us to investigate the issue further:

    • System Status Report which you can find via WooCommerce > Status
    • Fatal error logs (if any) under WooCommerce > Status > Logs.

    Please use https://pastebin.com/ or https://gist.github.com/ and share a link to that paste in reply here. Once we have more information, we’ll be able to assist you further

    Thread Starter cfm168

    (@cfm168)

    @shahzeenfarooq, Thank you for your response.

    I have just did the following:

    • WooCommerce transients – Clear
    • Expired transients – Clear
    • Clear template cache – Clear
    • Capabilities – Reset Capabilities
    • Clear customer sessions -Clear

    I will wait one day or two to see if still any errors happen.

    BTW, The Payments page under WooCommerce menu is blank https://ibb.co/fYrvDgHt

    And the Payments menu showing red alert mark: https://ibb.co/C3xrwZjJ

    Plugin Support LovingBro (woo-hc)

    (@lovingbro)

    Hi @cfm168,

    Thanks so much for following up and letting us know that you’ve cleared the WooCommerce caches and reset capabilities. That’s a great start, and it’s helpful that you’re giving it some time to see if the fatal error recurs.

    Regarding the Payments page under the WooCommerce menu appearing blank, could you please clarify whether this page was loading correctly before the update or if it has always been empty? Also, had you already configured any payment methods previously, or is this your first time accessing the page?

    Sometimes a blank Payments screen can be caused by a conflict with another plugin or an incomplete update, but I’ll be able to better guide you once I have a bit more context.

    As for the red alert with the number 1 on the Payments menu, that typically means there’s a pending setup step that needs attention. When you click on it, does it show any instructions or prompts? Or does it simply lead you to the same blank page?

    Lastly, could you please share your System Status Report from WooCommerce > Status > Get system report > Copy for support using https://quickforget.com or https://pastebin.com. That will help us understand your site environment and see what might be affecting the Payments section.

    Looking forward to your update so we can help you move forward!

    Thread Starter cfm168

    (@cfm168)

    Hi @lovingbro,

    Thank you for your help. Day one, no error report related to woocommerce. But the red alert with the number 1 on the Payments menu persists. When I click on it, it doesn’t show any instructions or prompts. And it simply lead to the same blank page.

    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi there!

    Thank you for sharing the more detials about the issue. To assist you further, I’d like to understand your site properly. Please share with us the necessary information below for us to investigate the issue further:

    • System Status Report which you can find via WooCommerce > Status
    • Fatal error logs (if any) under WooCommerce > Status > Logs.

    In the meantime please try to deactivate all plugin except woocommerce and see if you still face the same issue.

    Let me know how that goes.

    Thread Starter cfm168

    (@cfm168)

    Hi @shahzeenfarooq,

    This is the only error I found (related to theme twentyeleven) from the Status>Logs:

    Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /home/SorryHidedmysite/SorryHidedmysite.com/wp-includes/media.php:800

    Stack Trace


    1. image_get_intermediate_size(312, Array)
      /home/SorryHidedmysite/SorryHidedmysite.com/wp-includes/media.php:241

    2. image_downsize(312, Array)
      /home/SorryHidedmysite/SorryHidedmysite.com/wp-includes/media.php:975

    3. wp_get_attachment_image_src(312, Array, false)
      /home/SorryHidedmysite/SorryHidedmysite.com/wp-includes/media.php:1067

    4. wp_get_attachment_image(312, Array)
      /home/SorryHidedmysite/SorryHidedmysite.com/wp-content/themes/twentyeleven/image.php:105

    5. include(‘/home/SorryHidedmysite…’)
      /home/SorryHidedmysite/SorryHidedmysite.com/wp-includes/template-loader.php:106

    6. require_once(‘/home/SorryHidedmysite…’)
      /home/SorryHidedmysite/SorryHidedmysite.com/wp-blog-header.php:19

    7. require(‘/home/SorryHidedmysite…’)
      /home/SorryHidedmysite/SorryHidedmysite.com/index.php:17

    8. {main}
      thrown in /home/SorryHidedmysite/SorryHidedmysite.com/wp-includes/media.php on line 800

    Hi @cfm168 ,

    Thanks so much for reaching out — I’m really sorry to hear you’re running into this issue.

    Day one, no error report related to woocommerce. But the red alert with the number 1 on the Payments menu persists. When I click on it, it doesn’t show any instructions or prompts. And it simply lead to the same blank page.

    At the moment, we haven’t been able to replicate the same problem on our test site while running WooCommerce 9.8.5, so it’s possible that something specific in your site’s setup is triggering this behavior. However, it looks like some other folks are experiencing the same issue:
    https://wordpress.org/support/topic/payment-methods-not-displaying-anymore-in-wc-settings/

    To help get to the bottom of it, I’d recommend using the Health Check plugin and enabling Troubleshooting Mode. That’ll let you safely disable all other plugins and switch to storefront theme just for your user session, while keeping your live site unaffected for visitors.

    From there, activate only WooCommerce and see if the issue still happens. If it doesn’t, try re-enabling your other plugins one at a time — that can help pinpoint whether another plugin is conflicting.

    Let me know how it goes!

    Thread Starter cfm168

    (@cfm168)

    Hello,

    So far as today there are no Woocommerce related error reported in the status logs, but the Payments menu still displays (1) red mark https://ibb.co/C3xrwZjJ

    The only error report related to the theme in the status logs is same one as mentioned above.

    Please help. Thanks in advance!

    Hi @cfm168,

    Thanks for sharing that screenshot!

    What you’re seeing is expected, the red mark in the Payments menu appears when no payment methods have been set up yet. Once you add and configure at least one payment method (like WooPayments, PayPal, or Stripe), that indicator should disappear.

    Do you have any payment method configured?

    Thread Starter cfm168

    (@cfm168)

    Hello @mahfuzurwp,

    The Payments page under WooCommerce menu is blank https://ibb.co/fYrvDgHt

    I have both Paypal and Stripe added and configured from the installed plugins before the issue, and still working fine. The problem now is the Payment page under WooCommerce is blank and nothing can do.

    Plugin Support LovingBro (woo-hc)

    (@lovingbro)

    Hi @cfm168,

    Thanks for the update, and I understand how having a blank Payments page can be frustrating—especially since you’ve already configured PayPal and Stripe, and they’re still processing payments fine on the frontend.

    To help us dig further, could you please share your System Status Report from WooCommerce → Status → Get system report? You can paste it into https://pastebin.com or https://quickforget.com and send the link here.

    Also, just to confirm—have you already done a plugin and theme conflict test using the Health Check & Troubleshooting plugin as recommended earlier? This lets you temporarily disable other plugins and switch to a default theme like Storefront only for your session while keeping your site live for visitors. Let me know if you’ve tried that and what you found.

    Once we have that info, we’ll be able to guide you more precisely!

    Thread Starter cfm168

    (@cfm168)

    I have you already done a plugin and theme conflict test using the Health Check & Troubleshooting plugin.  During the troubleshooting mode (All plugins disabled but WC):

    1. The Payments page under WooCommerce menu is displayed and back to normal.
    2. Payments menu back to normal without displaying (1) red mark. This seems like WC forces to select one of the payment options from the Payments page.
    3. The following error report found:

    Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /home/SorryHidedmysite/SorryHidedmysite.com/wp-includes/media.php:800

    Stack Trace


    1. image_get_intermediate_size(312, Array)
      /home/SorryHidedmysite/SorryHidedmysite.com/wp-includes/media.php:241

    2. image_downsize(312, Array)
      /home/SorryHidedmysite/SorryHidedmysite.com/wp-includes/media.php:975

    3. wp_get_attachment_image_src(312, Array, false)
      /home/SorryHidedmysite/SorryHidedmysite.com/wp-includes/media.php:1067

    4. wp_get_attachment_image(312, Array)
      /home/SorryHidedmysite/SorryHidedmysite.com/wp-content/themes/twentyeleven/image.php:105

    5. include(‘/home/SorryHidedmysite…’)
      /home/SorryHidedmysite/SorryHidedmysite.com/wp-includes/template-loader.php:106

    6. require_once(‘/home/SorryHidedmysite…’)
      /home/SorryHidedmysite/SorryHidedmysite.com/wp-blog-header.php:19

    7. require(‘/home/SorryHidedmysite…’)
      /home/SorryHidedmysite/SorryHidedmysite.com/index.php:17

    8. {main}
      thrown in /home/SorryHidedmysite/SorryHidedmysite.com/wp-includes/media.php on line 800

    Hi @cfm168 ,

    Thanks so much for getting back to us.

    It’s a good sign that the Payments menu looks normal again and that the red notification is gone after running a conflict test — that usually points to a plugin or theme conflict. In this case, I’d suggest reactivating your plugins one by one (and switching back to your original theme if needed) to pinpoint which one might be causing the issue.

    As for the fatal error you’re seeing:

    Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /wp-includes/media.php:800

    This type of error typically means the code is trying to access a value as if it were an array, but it’s actually a string — and that leads to a fatal error in PHP 8 (where it used to just show a warning in earlier PHP versions like 7.4).

    From the error trace, it looks like the issue might be coming from your theme — specifically the way it’s handling images. Would you mind switching to the default Storefront theme temporarily to see if the error still happens? That’ll help confirm whether it’s the theme causing this or something else in the setup.

    Let us know how that goes — we’re here to help!

    Plugin Support Kay U a11n

    (@kingsleyinfo)

    We haven’t heard back from you in a while, so I’m going to mark this as resolved.

    If you have a few minutes, we’d love if you could leave us a review: https://wordpress.org/support/plugin/woocommerce/reviews/

    Thread Starter cfm168

    (@cfm168)

    The red mark https://ibb.co/C3xrwZjJ is caused by WooCommerce PayPal Payments v3.0.6 plugin (Author: WooCommerce).

    Turn off the plugin the red mark disappeared.

Viewing 15 replies - 1 through 15 (of 16 total)

The topic ‘Fatal error: Uncaught Error’ is closed to new replies.