allenshaw
Forum Replies Created
Viewing 4 replies - 1 through 4 (of 4 total)
-
Got it — thanks! I’ll go ahead and mark this Resolved now.
- You’re right, it was still active. I’ve disabled it.
- Adding
.*params+to the Exclusion Signs does exclude this ajax call from cleantalk checking (I’ve test that with s@cleantalk.org) - You mentioned:
> I’ve analyzed your site’s requests and noticed that some important parameters are not intercepted correctly by the plugin. This might cause the issue. Please do the following:
> 1. Update the Anti-Spam plugin by following this guide: https://cleantalk.org/help/update-wordpress
> 2. Set the cache update time on the site to no more than 24 hours (it’s important).
> 3. WordPress Admin Page → Settings → Security by CleanTalk → General settings → set the “Set cookies” option to “Alternative mechanism” → Save Changes.
> 4. Clear the cache.
Can you tell me what problem you observed which those steps would solve?
Thank you!
- I should have mentioned that at present we have the cleantalk plugin disabled on this site, pending resolution of the described issue. Does that explain what you’re seeing when you write “I’ve analyzed your site’s requests and noticed that some important parameters are not intercepted correctly by the plugin”?
- In more general terms, i belive that this AJAX call could be excluded if I used a regex matching the key name
paramsin the “Form Signs Exclusions” setting — is that correct?
Thank you,
A.Update: It appears that the latest version of the WP plugin (6.61) solved this problem (or else something else changed during the same period). Thanks for your help!
Viewing 4 replies - 1 through 4 (of 4 total)