Note: I have already read the solution here and the problem is in fact “fixed” using this solution. This question is not about finding the solution but how to implement the solution.
I am still stuck on version 5.3.2 due to this error on the login widget.
The fix that works for me is not regenerating assets in this plugin, not regenerating files in Elementor, not clearing the cache in my cache plugin (or server cache) but instead to clear my browser cache after performing the update.
However, this is also the fix for the thousands of members that I have on my site.
If I update to a version later than 5.3.2, I therefore get hounded by emails from my members saying that they can’t login.
This is even though I have a message underneath the login form stating that if they see this message that they should clear their browser cache (by using ctrl/cmd+shift+r on desktop).
However, I still end up getting tons of emails about difficulty logging in from mobile users as clearing cache on such devices is less intuitive and depends on browser, operating system etc.
Rather than dealing with all of those emails, I’ve just been staying on version 5.3.2.
Is there really no way for me to update to a later version of this plugin without asking my thousands of members to clear their browser cache on whatever device they use to login?
- The topic ‘Security token did not match – additional question’ is closed to new replies.