Security Alerts Pruning not working as intended

HI Robrave,

First off, thanks for your positive comments and I am sorry to hear you are encountering problems with our plugin.

So just to confirm, you have alerts which are older than 3 months, or more than 10000 alerts and they are not being deleted? Just to be clear in this case only the alerts that are older than 3 months, or the 10,001 and older alerts will be deleted.

If you would like to start afresh, I recommend you to:

1. Uninstall the plugin
2. Manually delete the following tables from the WordPress database (change the prefix if yours is different):
wp_wsal_metadata
wp_wsal_occurrences
3. Re-install the latest version of the plugin

Once you install the new version, if you notice that the pruning rules are not working please drop us an email on [email protected].

Looking forward to hearing from you

Hi,

I see. So that’s how it works. I’m sorry, I thought clicking Run Manually will clear the log completely.

So then I removed the check on Delete alerts older than.
Keep check on ” Keep up to” and add a value of 66.

I have 84 items on my log.

Clicked Run Manually. It is supposed to remove old items on log so that it will become from 84 to 66 right.

Nothing happened. It is still 84. Tried clicking Run Manually 3x. Nothing happened.

HI Robrave,

Yes that is how it works, i.e. run manually will enforce the policies you have there and then rather than waiting for the next scheduled execution.

As regards your scenario, I just reproduced it, hence I can confirm there is an issue there. Working on a fix as we speak, should issue an update tomorrow or early next week so please stay tuned.

Sorry for the mishap.

Thanks for the prompt replies.

Just confirming that I noticed this as well. I have a limit of 5,000 set but have 37,000 in my log.

Hello gents,

As confirmed before we have an issue with the pruning, though if you want here is a quick work around:

Disable one of the options (e.g. or restrict the alerts by number or by date rather than both) and the pruning will work.

Sorry for the delay in releasing the update but we are trying to squeeze in some other improvements with this release. Stay tuned with us and thanks for the support and patience.

Same issue here. For one of our sites the workaround worked fine. For another one, after deleting the tables mentioned above, if we try and reactivate the plugin the activation fails. In phpMyAdmin I can see the wp_wsal_metadata table filling up rapidly (several MB in seconds) until the site responds with “service unavailable.”

I think the issue might be related to old tables: are wp_wordpress_auditlog and wp_wordpress_auditlog_events still necessary? Deleting those as well prior to reinstalling seems to have solved the issue. Note that those tables are not recreated after the reinstall.

Okay, after some research it looks like those tables are no longer necessary: https://www.ads-software.com/support/topic/plugin-stopped-responding-after-new-version-100?replies=4. Dropping them as well should help the workaround work for anyone having issues still.

Hi Alex,

You can permanently delete the old tables mentioned below, they are no longer needed.

wp_wordpress_auditlog
wp_wordpress_auditlog_events

In the meantime please note that we are issuing a fix tomorrow, so stay tuned ??