The most recent request was denied because it contained an invalid security token. Please refresh the page and try again

Need help upgrading your Joomla! website or converting to Joomla! 3.x? Please consider the availability of third-party templates and extensions when deciding which Joomla version to use.

Moderator: General Support Moderators

Forum rules
Forum Rules
Absolute Beginner's Guide to Joomla! <-- please read before posting, this means YOU.
Forum Post Assistant - If you are serious about wanting help, you will use this tool to help you post.
User avatar
effrit
Joomla! Guru
Joomla! Guru
Posts: 594
Joined: Sun Nov 12, 2017 2:21 pm
Location: middle of Russia
Contact:

Re: The most recent request was denied because it contained an invalid security token. Please refresh the page and try a

Postby effrit » Sun Mar 11, 2018 1:18 pm

The problem is - this is common situation.
Even some experienced developers had it time to time, so i post here the solution to access in admin panel.
I guess this time it's the concrete module fault but i am not sure.

User avatar
sozzled
Joomla! Virtuoso
Joomla! Virtuoso
Posts: 4979
Joined: Sun Jul 05, 2009 3:30 am
Location: Canberra, Australia
Contact:

Re: The most recent request was denied because it contained an invalid security token. Please refresh the page and try a

Postby sozzled » Sun Mar 11, 2018 6:45 pm

@JAVesey: there are several elements that could be involved. The main culprit behind the "invalid security token" argument is PEBKAC but here's a list of the usual gang of suspects:

  • Sytem - Page Cache plugin: this is not to be confused with the core caching services whose settings are adjusted in the Global Configuration. This is a completely different thing. This plugin is disabled by default. This plugin is designed to be used with sites whose content rarely, if ever, changes. It's may not even be a good idea to enable this plugin if people are logging-in and logging-out of a website. If you do not know what the Sytem - Page Cache plugin does then do not enable it.

  • _session table: there can be times with the session data isn't properly sanitised; it may be necessary for the session data to be purged.

  • "advanced" caching services: Joomla's caching system should be agnostic about any host-based services used server side caching. If you use these caching systems then learn how they work before you use them.
Lastly, and in conclusion, guess what? No-one has provided even one FPA report that may allow the Joomla developers to get a handle on the problem!
https://www.kuneze.com/blog
Former member of Kunena project team
If you think I’m wrong then say “I think you're wrong.” If you say “You’re wrong!”, how do you know?


Return to “Migrating and Upgrading to Joomla! 3.x”

Who is online

Users browsing this forum: No registered users and 5 guests