robertabela

Hello. We have just released update 5.2.1. Before we do any further troubleshooting, can you please upgrade to the latest version and advise if the problem persists? In this update we’ve added a number of WooCommerce support improvements, so this might have been addressed.

Please keep us posted.

Hello @chartsheets

Please open your own forum thread so that we can support you. Thank you for your understanding and cooperation.

I am glad to read that @kevp75

We will be officially releasing the update within the next few minutes. Thank you for your cooperation.

By the way, if you like the plugin and our support please spare a minute to rate the plugin (URL: https://www.ads-software.com/support/plugin/wp-security-audit-log/reviews/). These ratings are really helpful.

Thanks a lot and have a great day.

Hello @kevp75

Thank you for reporting the issue. We have already prepared a patched version of the plugin which should address this. Since we cannot reproduce this in our test environemnt, can you please test the patch and let us know if that does the trick?

You can?download the patch from here. Thank you in advance for your cooperation and support.

Looking forward to hearing from you.

I am glad to read that @danielspain

We will be releasing 5.2.1 on the repo within this hour / next few hours. You will be notified in your dashboard about the update. Thank you for your cooperation and patience.

By the way, if you like our plugin and support, please rate the plugin. These ratings are really helpful.

Thank you again and have a good day.

Hello @clementtang

We already have a patch for this issue. Please download the patch from here. Within the next few minutes / hours we will be releasing update 5.2.1 publicly, however, you can download the patch to get the fix earler.

Please let us know if you need any additional assistance.

I am glad to read that @digitaliway

We are just waiting for a few other users to confirm this and we will upload the patch on the repo. It will be within the next few minutes, max an hour or so.

Thank you very much for your cooperation and patience. By the way, if you like the plugin and our support please rate the plugin. These ratings are really helpful.

Thank you again.

Thank you for the update @digitaliway

We have actually done some more fixes and have a new patch. Can you please download the path from here and let us know?

Thank you very much for your cooperation and patience.

We look forward to hearing from you.

Hello @danielspain

I am sorry to read about your issue. We have prepared a patched version of the plugin which should address this. Since we cannot reproduce this in our test environemnt, can you please test the patch and let us know if that does the trick?

You can download the patch from here.

We look forward to hearing from you.

Hello @digitaliway

We have updated the patch to address those notices. Can you please download the same patch again, install it and let us know?

You can?download the path from here.

Thank you very much for your cooperation.

Hello @digitaliway

We have been able to identify the issue and already have a patch available. We have tested it, but only in our environment, and we were not able to reproduce the problem.

Would you please be able to test the patch and report back to us if that solves the issue? You can download the path from here.

Looking forward to hearing from you.

Hello @digitaliway

I am sorry to read about your issue. A few other users have reported this so we are looking into this right now. We will be able to release a fix for this later on today, so please stay tuned.

Sorry if this has caused any inconvenience and thank you for your patience and cooperation.

Thank you for using our plugin @peterafarmer and @jlarisch

Later on today we are releasing update 5.2 of the plugin which will include a fix for this issue. So please stay tuned.

Sorry if this error has caused any inconvenience.

Thank you for using our plugin.

Can you please give us a bit more context on what happened, so we can better understand the issue?

1. Is the plugin still running or is this a show stopper bug?
2. Did this happen once or is it reported often?
3. Do you know the steps to reproduce it?
4. Can you reproduce the issue at will?

The more details you can share with us the easier it will be to track down the issue. Looking forward to hearing from you.

I am glad to read that. So this was a one-off issue. I have reported this to the developers so they include a fix in the next update.

Thank you for reporting this and should you have any other questions, or encounter something else please do not hesitate to ping us.

By the way, if you like our plugin and the support we provide, please spare a minute to rate the plugin. These ratings are really helpful.