-
In some posts, the ReAktions plugin is showing “illegal token” instead of a view number or a rating. This affects only certain posts and seems to be different for different users. (one user will see the error and another viewing the same post will not.)
Also the reaktions show correctly when viewing the page logged in to wordpress admin, but the same page viewed normally will show the error.
Browser developer tools is not showing an error.
Clearing browser cache does not solve.Hello
the token is a security code created by wordpress for each page, a unique ID to certify that the feedback is not being used for malicious attempts, such as SQL injections, and is a native default wordpress tool.To understand what can be causing this problem which we never saw before, I really need to see your site, where it happens and how to reproduce the problem.
Sometimes this can be cause from protocol mismatch.
For example, if you have set your site with https in the settings, and a user opens the page without https, the page may open anyway, but wordpress will manage the URL of the page as an illegal request, as the URl doesn’t match the declared one. This may lead to your issue for instance.
Looking forward for more detail wish you a nice day
regards
IgorThanks Igor. The site url is below
https://entertalkmedia.com/The posts that were giving me the error yesterday seem to be ok now, so I am not sure which ones to point you to try and replicate. I have a browser caching plugin enabled – I suspected that could be the culprit but clearing the browser cache didn’t seem to do anything for me.
Let me know if you come up with anything.
Thanks,Paul
Hi Paul, thanks for your kind and detailed feedback.
Actually, what I think could have happened, is that maybe the pages were cached and then (maybe) the protocol was switched to https.This may have caused the issue.
In the Love function there is a secret code to make sure the request comes from your same site.
If you cache the pages, that code stays binded to your site URL.
If you change it or if the same page is available with different protocols (http AND attps) the security code will result invalid, and cause this security block.
I think if you now cleared the cache you won’t see the issue anymore.
In case that happens, please let us know.
Thanks again for your kind collaboration
have a nice day
best regards
IgorThanks Igor! I figured it’s a caching issue. I’ll keep an eye on it.
There is another issue I ran into that I could use some help on.I was trying to change the Category template from “Default” to “Grid” and it wasn’t working. After some testing it looks like there is a conflict with a plugin I installed called Category Custom Background – that essentially let’s you add a background image to the category header. This is functionality I kind of need for the site.
If I disable the plugin, is there any way to add an image to the category from within Vlogger settings? (I couldn’t find any)
Conversely, is there any workaround to the plugin conflict you can offer that still allows for the grid template to work?Thanks
Hello there!
I’ve just checked the theme functionalities on a fresh installation and all work fine.
I made a video of it: https://youtu.be/BZbryiKqCmQI think it could be something related with third-party plugins you’ve installed on your website. Try to disable all the unnecessary plugins and check again if the Category Custom Background and category template setting work.
Keep me posted on this.
Thanks
The topic ‘Illegal Token for ReAktions’ is closed to new replies.