Hi @silasveta2012 ,
Thanks for the contact and asking an important question.
Actually we are using WordPress Nonce to secure the ajax request. Nonces are security tokens in WordPress.
Nonces can only be used once (hence “n once”), and they are only valid for a certain length of time: 12 hours by default.
On a cached page, the nonce can expire in the background while its ID is still present in the HTML source code of the page (Because of cache Plugin). If that happens, the HTML source is referencing an invalid nonce and things break.
Solution
=============
Here is the simple solution to avoid this nonce error (Posts found:parsererror) , You can set the lifespan of cache.
set your Cache lifespan option in (WP Rocket/other) plugins to a value below 12 hours; 10 hours would be a starting point, but you may have go down to 8 or even less.
Note : You can exclude the specific URL too from cache plugin.
Hope it will help you.
Thanks,
Trusty Plugins Team
Hello, in such a short time, the cache just doesn’t collect normally, you understand). In general, this is a problem of course, thank you for your work, but I think we need to look for another similar plugin. We even thought about buying the pro version, but now it’s not possible. I hope there will be an opportunity to fix this someday. All the best.
Hi @silasveta2012 ,
We have updated our plugin (1.9.4) and this issue has been fixed. Now you have setting option available to enable/disable nonce security.
Setting Available under Advanced Tab -> Security
Default : disabled
Please try now and let me know.
Thanks,
Trusty Plugins Team
Great news, but we have already switched to a paid plugin, with filters. It’s a pity that we were in a hurry, but we will keep in mind. Thank you and good luck to you. You have a great plugin and a great team!
