Posted: June 19, 2015 at 5:44 am
I am getting a number of users reporting that they are getting the following error message when they are clicking the link to their ticket: An error has occurred: Unable to complete the request because the token is invalid. EED_Messages – run – 149. Some of these users appear to have been having issues with other aspects of the booking process as well. So far I have ascertained that the browser for one user is Internet Explorer, though I don’t know the version. Nick |
|
Hi Nick, Are you running a stable version of Event Espresso? Which version number is active? |
|
Ah, that might be the issue. I am running 4.7.0.beta.004. |
|
Is is possible to downgrade to the latest stable version or will this mess things up? I upgraded to the beta in order to be able to use the promotions add on, but now realise that I shouldn’t have done this in a live site. |
|
Hi Nick, You can upgrade to the latest stable by following these steps: 1) Backup the database Along with that, please make sure that there isn’t any server level caching set up either by a plugin or through the server’s configuration. |
|
Hi Josh, Thanks. I have updated to 4.7.2 and will continue to monitor whether users have difficulty accessing the ticket. Regarding caching plugins, I am using W3 Total Cache, but I have the necessary pages added for EE registration. Should I disable this plugin? Nick |
|
Hi Nick, you can continue to use W3 total but be sure to keep those no-caching rules in place. — |
|
Nick, Are you using W3 Total cache to enable object caching? Better yet, can you tell us which methods of caching are currently enabled, besides page caching? |
|
Yes, I am using W3 Total Cache for Page Cache, Object Cache and Minify. There doesn’t appear to be a slug that I can add for ticket pages, like with registration pages. |
|
Hi Nick, I ran some searches for the error message that you shared and did not find any other reports. Could you briefly deactivate the caching services through W3 total cache and then turn off the plugin and then re-test? Note that deactivating the plugin alone does not turn off caching services. — |
|
The support post ‘Invalid token’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.