• Resolved marinow1991

    (@marinow1991)


    Hi, after updating to the latest version of Woo I started getting this error. I get the error every second

    [Thu Oct 05 13:55:06.624569 2023] [proxy_fcgi:error] [pid 175741:tid 140261795546880] [client 207.46.13.154:0] AH01071: Got error 'PHP message: PHP Fatal error:  Uncaught TypeError: strstr(): Argument #1 ($haystack) must be of type string, WP_Error given in /home/armadabg/web/armadabg.eu/public_html/wp-includes/functions.php:1144\nStack trace:\n#0 /home/armadabg/web/armadabg.eu/public_html/wp-includes/functions.php(1144): strstr()\n#1 /home/armadabg/web/armadabg.eu/public_html/wp-includes/functions.php(1217): add_query_arg()\n#2 /home/armadabg/web/armadabg.eu/public_html/wp-content/plugins/woocommerce/includes/widgets/class-wc-widget-layered-nav.php(423): remove_query_arg()\n#3 /home/armadabg/web/armadabg.eu/public_html/wp-content/plugins/woocommerce/includes/widgets/class-wc-widget-layered-nav.php(187): WC_Widget_Layered_Nav->layered_nav_list()\n#4 /home/armadabg/web/armadabg.eu/public_html/wp-includes/class-wp-widget.php(394): WC_Widget_Layered_Nav->widget()\n#5 /home/armadabg/web/armadabg.eu/public_html/wp-includes/widgets.php(837): WP_Widget->display_callback()\n#6 /home/armadabg/web/armadabg.eu/public_html/wp-content/themes/flatsome/woo...'
    

    https://prnt.sc/4fJSfcRq5KGa

Viewing 1 replies (of 1 total)
  • Hi @marinow1991

    after updating to the latest version of Woo I started getting this error. I get the error every second

    From what I understand, you’re experiencing a PHP error after updating to the latest version of WooCommerce. It seems to be related to the ‘strstr()’ function, which is expecting a string but receiving a WP_Error instead. This error appears to be happening quite frequently.

    There could be several reasons behind this issue. Here are a few steps you can take to try and fix it:

    1. Update all plugins and themes: Make sure all your plugins and themes are up-to-date. Older versions might not be compatible with the latest version of WooCommerce, which could be causing the error.
    2. Deactivate all plugins except WooCommerce: This will help figure out if another plugin is causing the problem. If the error goes away after deactivating other plugins, turn them back on one at a time to find the culprit.
    3. Switch to a default WordPress theme: This can help determine if your current theme is causing the issue. If the error goes away when you switch to a default theme, it means the problem lies with your current theme. Check out this handy guide on how to test for conflicts: ?? How to Test for Plugin and Theme Conflicts.
    4. Check for custom code: If you’ve added any custom code to your website, try removing it temporarily to see if that’s the problem.
    5. Enable Debugging: If the issue still isn’t resolved, turn on debugging in WordPress. This can help pinpoint the root cause. You can enable debugging by adding these lines to your wp-config.php file:
    define( 'WP_DEBUG', true );
    define( 'WP_DEBUG_LOG', true );
    define( 'WP_DEBUG_DISPLAY', false );
    @ini_set( 'display_errors', 0 );

    This will create a debug.log file in your wp-content directory, which will log any PHP errors or notices. For a more detailed guide on enabling debugging in WordPress, check out this link: ?? Debugging in WordPress.

    If the problem persists after trying these steps, please share more details, such as the exact error messages you’re seeing when debug mode is on. This will help us identify and solve the problem more effectively.

    Also, it would be really helpful if you could share your site’s System Status report. This will give us a better understanding of your site’s setup and help us identify the problem. You can find it via WooCommerce > Status. Select Get system report and then Copy for support.

    Once you’ve collected this information, please paste it in a Code block in your reply, or use https://pastebin.com to paste it and share the link with us.

    Thank you for your patience and cooperation! We’re here to help you resolve this issue.

Viewing 1 replies (of 1 total)
  • The topic ‘Error in the php after update Woo’ is closed to new replies.