Hi @srogers1,
I’m aware of this issue on certain server configurations, but I haven’t yet found time to release an update 🙂 Til then you can do a small change in code to fix the problem.
Change this line in rate-my-post/public/class-rate-my-post-public.php
if( ( $token === $db_token ) && ( $db_token != '-1' ) && ( $acceptableTime > $currentTime ) ) { // tokens match, time window is ok and rater is eligible to give feedback
to
if( ( $token === $db_token ) && ( $db_token != '-1' ) ) { // tokens match, time window is ok and rater is eligible to give feedback
Regards,
Blaz
Also officially fixed in version 3.1.0 🙂
Hello
I’m still getting this error. but I’ve found that after cleaning website cache, the error disappears.
I’m using Litecache
Hi @victormorenos,
are you sure it’s invalid token? Because you issues sound more like invalid nonce error. The invalid nonce error will appear if a page is cached for more than 24 hours – that’s just how WordPress nonces work. So, it’s important to set TTL for less than 24 hours.
Blaz
Hi @blazk
Thank you for your reply.
I’ve tried to set TTL to less than 24 hour but it didn’t worked.
When I push a new post or post update, after some hours it begins to get “invalid token error”.
But, after cleaning the cache, it backs to the normal. No matter how much time passes, it will work.
On my first post, the plugin is working perfectly after I cleaned up the cache for the first time. If a push a new update to it, propably, I’ll need to clean up the cache again in 8 or 9 hours.
Addtional info: The error in portuguese is: “Código de verificação inválido!” (I think it means “invalid token error” in english, isn’t it?)
Thank you for supporting 🙂
