CleanTalk SFW update error: updateWorker: Wrong update ID.

Hi,

I will ask our developers about this. We will contact you within 1-2 business days.

Hello @_kom__,
Thank you for waiting.

Please do the following to fix this issue:
1) Save the settings in our plugin.
2) If step 1 did not help, then reinstall our plugin.

Please let us know the results.

Got the same issue on local development environment. Reinstalling removed the notifications. But this should never be the final solution.

@janez zibelnik Please wait for 1 day and try to re-save the plugin's settings.

Did it help?

I've reinstalled version 9.5.0 both on local and production sites.
The warning has gone.
After upgrade to 9.6.1 there is no warning too. All protections (spam and firewall) seem to work as designed.
But as I mentioned before there's no version changes in dashboard: the displayed version is still 9.5.0 after more than 24 hours.

@_kom__ We've fixed the version issue. It should be corrected automatically.

App version in dashboard chanded, thank you.

You're welcome! Feel free to contact us if you need any help.

Automatically closed - issue fixed for 2 weeks with no activity.

CleanTalk SFW update error: updateWorker: Wrong update ID. Please, save settings to run new SFW update and wait for an hour..

This issue still appears from time to time and full module uninstall, cache clear and reinstall is needed. In some cases, uninstall causes WSOD before being able to fully uninstall too.

Now uninstall fails every time. Is there any other way to fix the SFW update error?

I also don't think this was fixed. Should I open new ticket, or should this one be re-opened?

Hello klemendev.

We need additional details about your website. Please contact us via our private Ticket System and add there a link to this issue: https://cleantalk.org/my/support/open.

Ok, will do so. Thanks!

We fixed the issue. The edits are contained in the attached archive.

This seems to work since it disables SFW updates if SFW is off. Since we don't use it right now, this is fine. If we need to use it, we may need to look into a more proper solution later down the road as this technically just "masks" the problem

That's right, the patch disables the cron task to update SFW if the SFW option is turned off. If SFW is enabled, the update should occur without errors.

That's right, the patch disables the cron task to update SFW if the SFW option is turned off. If SFW is enabled, the update should occur without errors.

I see, thanks for the clarification! In this case, this patch looks good and can be merged :)