We have had quite a few reports of issues (here and on the forum) after updating that are caused by cache as it caches admin as well as site components - especially with the Page Cache plugin
If the joomla update process cleared the cache it would resolve this once and for all
Rel_Number | 0 | ⇒ | 9568 |
Relation Type | ⇒ | Related to |
Not talking about the browser cache but the joomla cache files /cache
On 28 Mar 2016 9:42 am, "zero-24" notifications@github.com wrote:
Hmm i'm not sure can joomla clear the browser cache of an client? I guess
the only thing we can do is to have at the end of every assest a version
string that comes from the joomlaversion or the MD5CHECKSUM file that
handel this version string.—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#9626 (comment)
Ah ok. This should be possible. Maybe in the script.php i can have a look later
See #9568 for examples of some issues caused because of joomla cache
@brianteeman see: #9628
@andrepereiradasilva i have no idea how opcache / apcu works or how to test that it works. ;)
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-03-28 10:09:33 |
Closed_By | ⇒ | brianteeman |
@brianteeman I updated my site from Joomla 3.5.0 to Joomla 3.5.1 and this problem still happen. I tried remove all Joomla Cache file but no better.
1 - Login first time is successful.
2 - Logout and re-login. I get notice "The most recent request was denied because it contained an invalid security token. Please refresh the page and try again.".
Solution: Disable Plugin - Joomla Cache.
I am getting the same issue as described by sonvnn.
Is Disabling Joomla Page Cache an actual solution?
This isn't a 3rd party plugin, so any update to the core should be compatible with it, no?
My solution which seems to be holding at the moment, is to exclude the behind login URLs from the Page Cache so that we can still take advantage of Page Caching.
Joomla version, 3.5.1.
Reg Issue: "The most recent request was denied because it contained an invalid security token. Please refresh the page and try again."
Agree with tgetgood13. Adding Log In, Log Out to "Exclude Menu Items" In System-Page Cache plugin settings fixed the token issue for me. Before that I had to delete entries from _session table, after which users were able to login, but not able to re-login
Found something.
Akeeba backup making problems for me.
1. Make backup
2. Turn off System - Backup on update
3. Update
4. Turn on System - Backup on update
That's because you do not have the latest version if akeeba backup you need 5.1.4
Hmm i'm not sure can joomla clear the browser cache of an client? I guess the only thing we can do is to have at the end of every assest a version string that comes from the joomlaversion or the MD5CHECKSUM file that handel this version string.