Syntax error (%d not replaced)

HI Luis,

Thank you for using our plugin and sorry to see you are encountering problems.

Can you please give me a bit of an overview about your problem by answering my questions?

1. Is it a new install or an upgrade?
2. It used to work before and it stopped during an upgrade?
3. When are you exactly getting this error, i.e. what are you trying to access?

Looking forward to hearing from you.

Hi Robert,

To answer your questions:

1. This is an upgrade. I haven’t yet tried uninstalling and reinstalling the plugin, didn’t seem to me it would solve a token replacement issue, but I can do it anyway.

2. I’ve had query issues with this plugin in the past (mostly queries not supported by the database engine), but it’s the first time I’ve encountered this one.

3. I have to get back to you on this later if you need specifics, but one of the situations that triggers this error is when running a cron job (initiated by a crontab script rather than an HTTP request to WordPress).

Thanks!

Hi Luis,

Thank you for the details. It would be good if you can get back to me with more information though we will still look into what this issue could be.

Will keep you posted.

Can you already fix it, please? The logs are filling up with the errors:

WordPress database error You have an error in your SQL syntax;
check the manual that corresponds to your MySQL server version
for the right syntax to use near
'%d ORDER BY created_on ASC LIMIT  1470'
at line 1 for query
SELECT * FROM x_wsal_occurrences WHERE created_on < %d
ORDER BY created_on ASC LIMIT  1470
made by do_action_ref_array, call_user_func_array,
WpSecurityAuditLog->CleanUp, call_user_func,
WSAL_Loggers_Database->CleanUp, WSAL_DB_OccurrenceQuery->Delete

HI Tigr this is a separate issue from what Luis reported hence can you please open a separate ticket?

Having said that we were not able to reproduce any of the issues mentioned about hence these must be specific to your scenarios, maybe there is a conflict with another plugin or so.

Therefore can you please contact us on [email protected] so we can look further into each issue?

Looking forward to hearing from you.

Right. Removed the plugin, dropped the tables with audit and wsal, removed all options with wsal in them. Reinstalled the plugin, now seems to work without errors. There must be something messed up sometimes during update, that’s why you cannot reproduce it.

HI Tigr,

I am glad your issue is solved. By the way we do test updates as well.

Thanks for the update.

HI Luis Rodrigues,

We will have a fix for your issue in the next update of the plugin. Thanks for reporting it and stay tuned with us.

The next update should be available early next week.

Hi Tigr,

We have a fix for your issue as well. Can you please drop us an email on [email protected] so we can send you an interim build for further testing?

Looking forward to hearing from you.