• Resolved strarsis

    (@strarsis)


    When editing products, this plugin causes a fatal error that prevents loading the product edit page:

    Uncaught Error: Class "WSAL_Models_OccurrenceQuery" not found in [...]/plugins/wp-activity-log-for-woocommerce/wp-security-audit-log/sensors/class-woocommerce-sensor.php:3300

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

    (@robert681)

    Hello Strarsis,

    Thank you for using our plugin. I am sorry to read about your issue.

    Let’s start with some basic troubleshooting: Can you please install the latest version of WP Activity Log (4.6) and uninstall this extension?

    This extension has been merged into the plugin’s core, so it is no longer needed.

    When you do so, dos the issue persist?

    I’m seeing the same behavior. Already running version 4.6. Disabled fixes the problem, but obviously would like this plugin enabled.

    Error Details
    
    =============
    
    An error of type E_ERROR was caused in line 3300 of the file /var/www/vhosts/xxx.org/httpdocs/wp-content/plugins/wp-activity-log-for-woocommerce/wp-security-audit-log/sensors/class-woocommerce-sensor.php. Error message: Uncaught Error: Class 'WSAL_Models_OccurrenceQuery' not found in /var/www/vhosts/xxx.org/httpdocs/wp-content/plugins/wp-activity-log-for-woocommerce/wp-security-audit-log/sensors/class-woocommerce-sensor.php:3300
    
    Stack trace:
    
    #0 /var/www/vhosts/xxx.org/httpdocs/wp-content/plugins/wp-activity-log-for-woocommerce/wp-security-audit-log/sensors/class-woocommerce-sensor.php(3261): WSAL\Plugin_Sensors\WooCommerce_Sensor::was_triggered()
    
    #1 /var/www/vhosts/xxx.org/httpdocs/wp-includes/class-wp-hook.php(310): WSAL\Plugin_Sensors\WooCommerce_Sensor::editing_product()
    
    #2 /var/www/vhosts/xxx.org/httpdocs/wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters()
    
    #3 /var/www/vhosts/xxx.org/httpdocs/wp-includes/plugin.php(517): WP_Hook->do_action()
    
    #4 /var/www/vhosts/xxx.org/httpdocs/wp-admin/edit-form-advanced.php(463): do_action()
    
    #5 /var/www/vhosts/xxx.org/httpdocs/wp-admin/post.php(206): require('/var/www/vhosts...')
    
    #6 {main}
    
      thrown

    yeah, had to disable on 5 sites… not good.

    Plugin Support robertabela

    (@robert681)

    Hello everyone, we have escalated this issue and the developers are looking into it. We’ll keep you posted.

    Plugin Support robertabela

    (@robert681)

    Hello everyone,

    Just to confirm you are running the right setup:

    Up until update 4.5.3 you needed WP Activity Log and this extension (WP Activity Log for WooCommerce) installed.

    Since version 4.6 we have merged this extension to core, so you should have the following:

    WP Activity Log – activated
    WP Activity Log for WooCommerce – deactivated and uninstalled. This is no longer needed, this functionality is available in core now.

    Can you confirm if you have the above setup? Do you get the error with the extension deactivated?

    Looking forward to hearing from you.

    Thread Starter strarsis

    (@strarsis)

    So I found this message on the main WP Activity Log settings page:

    In WP Activity Log 4.6 we have merged the third party plugins activity log extensions in the plugin's core. If you have any of these installed, the plugin has already deactivated them during the update. You can now delete / uninstall these extensions if you have them installed.

    Then those extension plugins can be removed and this would fix the issue.

    • This reply was modified 9 months, 1 week ago by strarsis.

    Disabling the extra plugins worked for my situation. As the notes suggested they were disabled automatically, this was indeed not the case on any my installations. I had to manually disable and remove.

    Thanks for the quick help.

    Plugin Support robertabela

    (@robert681)

    Indeed, all the extensions for third party plugins should be removed. Clearly it seems that in some cases the plugin failed to deactivate them automatically unfortunately.

    Just wanted to add that this should have been communicated more explicitly.
    Just spent hours trying to figure out why my product image would not save.

    Eventually, it was the WC log that hinted me towards your plugin’s errors.
    What is the point of deactivating an extension plugin and not removing it alltogether when folks could easily reactivate it later, assuming it has still value.

    Either communicate more clearly (persistent banner until the plugin is removed) or have the core plugin not just deactivate but delete the extension plugin, I would say…

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