WP Security Audit Log
[resolved] Problem when upgrade to 1.0.0 version (2 posts)

  1. array064
    Posted 1 year ago #

    After I upgraded to version 1.0.0 (from 0.6.3 version) of this plugin, I found the following error message:

    Table 'MYDB.DBPREFIX_wsal_occurrences' does not exist

    And the following is an example of an error tracking from newrelic for the above error:

    in mysql_query called at /home/SITEFOLDER/httpdocs/wp-includes/wp-db.php (1619)
    in wpdb::_do_query called at /home/SITEFOLDER/httpdocs/wp-includes/wp-db.php (1523)
    …ed at /home/SITEFOLDER/httpdocs/wp-content/plugins/w3-total-cache/lib/W3/
    Db.php (179)
    …ed at /home/SITEFOLDER/httpdocs/wp-content/plugins/w3-total-cache/lib/W3/
    Db.php (307)
    …ed at /home/SITEFOLDER/httpdocs/wp-content/plugins/w3-total-cache/lib/W3/
    Db.php (95)
    …ed at /home/SITEFOLDER/httpdocs/wp-content/plugins/w3-total-cache/lib/W3/
    Db.php (434)
    … /home/SITEFOLDER/httpdocs/wp-content/plugins/w3-total-cache/lib/W3/
    DbCache.php (143)
    …ed at /home/SITEFOLDER/httpdocs/wp-content/plugins/w3-total-cache/lib/W3/
    Db.php (95)
    in W3_Db::query called at /home/SITEFOLDER/httpdocs/wp-includes/wp-db.php (1824)
    ActiveRecord.php (307)
    AuditLog.php (98)
    in WSAL_Views_AuditLog::AjaxRefresh called at ? (?)
    …call_user_func_array called at /home/SITEFOLDER/httpdocs/wp-includes/
    plugin.php (470)
    in do_action called at /home/SITEFOLDER/httpdocs/wp-admin/admin-ajax.php (82)

    After that, I could not open the "Audit Log Viewer" page (error 503 from varnish, because the request timed out).

    So, for a while I deactivate this great plugin, until the next new version.

    Additional information:

    WordPress version: 3.9.1
    OS: Linux
    Server: Apache/2.2.22 (Ubuntu)
    PHP: v5.3.10-1ubuntu3.11
    MYSQL: v5.5.37-0ubuntu0.12.04.1-log
    Important used plugin: W3 Total Cache


  2. WPWhiteSecurity
    Plugin Author

    Posted 1 year ago #

    Hi Array,

    We can confirm there was an issue with the upgrade script and sorry if it caused any inconvenience.

    If you disable and re-enable the plugin it will work :) A fix is available in the upcoming update which is due to be released tomorrow or early next week.

    Thank you again for using our plugin.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic


No tags yet.