• Resolved jona7hanh

    (@jona7hanh)


    My website was working fine, but suddenly showing Critical Error. Having disabled all plugins and re-enabling them one by one it seems the error is being caused by WooCommerce.

    The log is as follows:
    PHP Fatal error: Uncaught TypeError: strpos(): Argument #1 ($haystack) must be of type string, array given in /www/naturalhealthdynamics_990/public/wp-content/plugins/woocommerce/src/Admin/RemoteInboxNotifications/ComparisonOperation.php:49

    The page I need help with: [log in to see the link]

Viewing 10 replies - 1 through 10 (of 10 total)
  • Absolutely the same I had this night!
    See my topic earlier.
    It seems this night something triggered this error to be arised.
    But it is useless…they do not answer because we did not pay for their plugin…
    I do not know what to do.


    Thread Starter jona7hanh

    (@jona7hanh)

    Guess we have to wait for them to fix it or issue an update?

    Is there any more stable alternative to Woo?
    I hate such hickups….

    Thread Starter jona7hanh

    (@jona7hanh)

    No that I’m aware of – unless you go the Shopify route

    nustart

    (@nustart)

    If you need to get you site up and running, I have just added

    return false;

    To line 23 (at the top of the function) at: /wp-content/plugins/woocommerce/src/Admin/RemoteInboxNotifications/ComparisonOperation.php

    public static function compare( $left_operand, $right_operand, $operation ) {
    
    //Added this as a tempfix
    return false;
    		

    This is a short-term emergency hack and I would expect Woocommerce support to issue an update to overwrite the ComparisonOperation.php to fix the code problem , but if you need something just to get your site up, this has worked for me
    [But, this could impact notifications from your site, so only use with caution and keep an eye out for Woocommerce official fx) ]

    • This reply was modified 10 months ago by nustart.
    dilbert16588

    (@dilbert16588)

    Having the same issue today suddenly. It appears some have “resolved” the critical error issues by reverting to an older version.

    I only have one product currently but would rather keep my shop enabled than deactivate WooCommerce. The noted temp fix from nustart worked for me – until they issue an actual fix.

    Plugin Contributor Albert Juhé Lluveras

    (@aljullu)

    Thanks for reporting this, folks! The issue has been fixed in WooCommerce 8.5.2, which was released a few hours ago:

    https://developer.woo.com/2024/01/25/woocommerce-8-5-2-fixes-to-remote-inbox-notifications/

    Plugin Support ckadenge (woo-hc)

    (@ckadenge)

    Hi all.

    Could you please help confirm if the issue was resolved after updating to 8.5.2?

    Thread Starter jona7hanh

    (@jona7hanh)

    Yes it was ??

    Plugin Support ckadenge (woo-hc)

    (@ckadenge)

    Hi @jona7hanh,

    Glad to hear it – thanks for letting us know!

    I’ll mark this thread as resolved now. If you have any further questions, I recommend creating a new thread.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Critical Error: WooCommerce RemoteInboxNotifications’ is closed to new replies.