Uncaught Error: Call to a member function get_sku() on bool

  • Resolved ellmann creative

    (@ellmanncreative)


    2 years, 11 months ago

    Uncaught Error: Call to a member function get_sku() on bool in ((:::SNIP:::))/wp-content/plugins/wp-activity-log-for-woocommerce/wp-security-audit-log/custom-sensors/WSAL_Sensors_WooCommerce.php:511
Stack trace:
#0 ((:::SNIP:::))/wp-content/plugins/wp-activity-log-for-woocommerce/wp-security-audit-log/custom-sensors/WSAL_Sensors_WooCommerce.php(488): WSAL_Sensors_WooCommerce->get_product_sku(2462)
#1 ((:::SNIP:::))/wp-content/plugins/wp-activity-log-for-woocommerce/wp-security-audit-log/custom-sensors/WSAL_Sensors_WooCommerce.php(357): WSAL_Sensors_WooCommerce->EventCreation(Object(WP_Post), Object(WP_Post))
#2 ((:::SNIP:::))/wp-includes/class-wp-hook.php(307): WSAL_Sensors_WooCommerce->EventChanged(2462, Object(WP_Post), false)
#3 ((:::SNIP:::))/wp-includes/class-wp-hook.php(331): WP_Hook->ap

    This happens when I publish/unpublish a product, move it to trash, restore it from trash etc. The requested effect does still happen (as evidenced in the product being unpublished, moved to/from trash etc.), but it’s a PITA to go through HTTP 500 each and every time.

    Tested on both staging and live, happens on both (different hosting).

    WSAL for Woo v1.4.0 (WSAL v4.4.1) @ WP v5.9.3 with Woo v6.3.1

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Support robertabela

    (@robert681)

    Hello @ellmanncreative

    Thank you very much for using our plugin.

    I am sorry to read about your issue. Today we released update 1.4.0 of this extension, which features a good number of improvements and fixes a number of known issues. Can you please update to version 1.4.0 and advise if the problem persists?

    If you’d like to now what is new, improved and fixed in this update please refer to the Activity Log for WooCommerce release notes.

    Looking forward to hearing from you.

    Thread Starter ellmann creative

    (@ellmanncreative)

    I can confirm this issue is present everywhere with WSAL for Woo at version v1.4.0. Not sure if it was present before, but it’s showing up in all of my installs now.

    Current solution is to disable the plugin and wait for a new version. Haven’t tried rolling back to see when the issue first started.

    Plugin Support robertabela

    (@robert681)

    Hello @ellmanncreative

    After reviewing the code and the error messages with the developers it seems that the error in your first post is not the “full” error message. Can you please confirm this? If yes, can you share all the log?

    We think that there is another plugin that is conflicting / interfering with our plugin from getting the SKU. We are only running a function provided by WooCommerce so the $product variable should be correct.

    We can give you a patch to “silence” the error but that would not fix the issue.

    Looking forward to hearing from you.

    Same problem here, any solution?

    Thread Starter ellmann creative

    (@ellmanncreative)

    @robert681 the only component I removed is the full folder path to WP’s installation. Everything else is provided as it was reported by the webserver.

    Thread Starter ellmann creative

    (@ellmanncreative)

    Okay, so I have a testbed WP install, and I replicated all plugins we’re commonly using.

    It looks like the issue is triggered when Sucuri Security is also active… but that’s not the whole story. I deactivated all plugins, then re-activated them again… and the problem is gone on the test site – I can’t re-trigger it now.

    Conversely, on the staging and live sites, the problem is still there regardless of what I deactivate and reactivate.

    It’s one of those issues.

    I confirm the problem: in my case there is All In One WP Security

    Plugin Support robertabela

    (@robert681)

    Hello everyone,

    We have addressed this issue in update 1.4.1. So please download the latest version of this extension to address the issue.

    Thank you very much for using our plugin and sorry for the inconvenience. If there is something else we can assist you with, please do not hesitate to ask.

    Have a great day.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Uncaught Error: Call to a member function get_sku() on bool’ is closed to new replies.