Update error 4.4.2

  • Resolved zavastin

    (@zavastin)


    2 years, 8 months ago

    Got this error after last update

    Fatal error: Uncaught Error: Class 'WSAL_Adapters_MySQL_Occurrence' not found in /home3/********/public_html/wp-content/plugins/wp-security-audit-log/classes/Connector/MySQLDB.php:192 Stack trace: #0 /home3/********/public_html/wp-content/plugins/wp-security-audit-log/classes/Models/ActiveRecord.php(163): WSAL_Connector_MySQLDB->get_adapter('Occurrence') #1 /home3/********/public_html/wp-content/plugins/wp-security-audit-log/classes/Models/ActiveRecord.php(258): WSAL_Models_ActiveRecord->get_adapter() #2 /home3/********/public_html/wp-content/plugins/wp-security-audit-log/classes/Loggers/Database.php(91): WSAL_Models_ActiveRecord->save() #3 /home3/********/public_html/wp-content/plugins/wp-security-audit-log/classes/AlertManager.php(654): WSAL_Loggers_Database->log(5004, Array) #4 /home3/********/public_html/wp-content/plugins/wp-security-audit-log/classes/AlertManager.php(353): WSAL_AlertManager->log(5004, Array) #5 /home3/********/public_html/wp-content/plugins/wp-security-audit-log/classes/AlertManager.ph in /home3/********/public_html/wp-content/plugins/wp-security-audit-log/classes/Connector/MySQLDB.php on line 192

    Any idea how to solve this?

    Thanks!

    Using version 4.4.2
    Woocomm 6.5.1
    PHP 7.4.30

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

    (@robert681)

    Hello @zavastin

    Thank you for using our plugin.

    I am sorry to read about your issue.

    When do you get this error? Right after upgrading and you can’t use the plugin / website, or only when you do something specific?

    Also, did you try deactivating the plugin and activating it again, does it help?

    Looking forward to hearing from you.

    Thread Starter zavastin

    (@zavastin)

    I got this error after updating.

    Deactivating and activating didn’t do the trick.

    I’m still getting this

    /*******/public_html/wp-content/plugins/wp-security-audit-log/vendor/composer/../../classes/Upgrade/Upgrade_43000_To_44400.php): failed to open stream: No such file or directory in /home3/*******/public_html/wp-content/plugins/code-snippets/vendor/composer/ClassLoader.php on line 480

Warning: include(): Failed opening '/home3/******/public_html/wp-content/plugins/wp-security-audit-log/vendor/composer/../../classes/Upgrade/Upgrade_43000_To_44400.php' for inclusion (include_path='.:/opt/alt/php74/usr/share/pear') in /home3/******/public_html/wp-content/plugins/code-snippets/vendor/composer/ClassLoader.php on line 480
    Plugin Support robertabela

    (@robert681)

    Hello @zavastin

    I think we have spotted the issue. Can you please uninstall the plugin, make sure the plugin directory is deleted (/wp-content/plugins/wp-security-audit-log) and then install it again by downloading it from the repository.

    We’ve seen cases in which an upgrade file we replaced in the past was not deleted and replaced due to capitalization in the filename (our mistake).

    By the way, the logs and the plugin settings will be retained upon uninstall and install, so you won’t lose any data. Having said that, we always recommend you to backup the website.

    Can you please tell us if that solves the issue?

    Thread Starter zavastin

    (@zavastin)

    Thanks, I will try,

    But please tell me if I have to uninstall and delete the plugin extension (WP Activity Log plugin extension for WooCommerce)

    Plugin Support robertabela

    (@robert681)

    Hello @zavastin

    No, you do not have to uninstall the plugin extension as well. Just the main plugin – WP Activity Log.

    Thread Starter zavastin

    (@zavastin)

    Looks like now it’s back to normal…

    Plugin Support robertabela

    (@robert681)

    I am glad to hear that @zavastin

    Should there be anything else, do not hesitate to ask. By the way, please do not forget to rate our plugin and service. These ratings really help us and the plugin.

    Have a great day.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Update error 4.4.2’ is closed to new replies.