[#10255] - The most recent request was denied because it contained an invalid security token.
- Closed
- 5 May 2016
- Medium
- Build: master
- # 10255
Steps to reproduce the issue
Login to site or admin
Wait until the end of the session
Reload page, and automatic get to the login page
Try login
Expected result
Log on website
Actual result
Get empty page with text:
"The most recent request was denied because it contained an invalid security token. Please refresh the page and try again."
or
"Последний запрос был отклонён, поскольку он содержит неправильный параметр безопасности (security token). Пожалуйста, обновите страницу и попробуйте еще раз."
System information (as much as possible)
The platform on which works PHP Linux s14.thehost.com.ua 3.13.0-83-generic # 127 ~ precise1-Ubuntu SMP Fri Mar 11 12:53:08 UTC 2016 x86_64
The database version 5.6.29
Database coding utf8_general_ci
Encoding database connection utf8mb4_general_ci
Version PHP 5.3.10-1ubuntu3.22
Apache Web Server
The interface between the web server and PHP apache2handler
Joomla version! Joomla! 3.5.1 Stable [Unicorn] 05-April-2016 22:45 GMT
Joomla version! Platform Joomla Platform 13.1.0 Stable [Curiosity] 24-Apr-2013 00:00 GMT
The user's browser Mozilla / 5.0 (Windows NT 10.0; WOW64) AppleWebKit / 537.36 (KHTML, like Gecko) Chrome / 50.0.2661.94 Safari / 537.36
Additional comments
How can I skip the blank screen and no sign of this error?
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-05-05 17:01:37 |
| Closed_By | ⇒ | brianteeman |
So, this is no problem of Joomla? Is this my personaly problem?
| Labels |
Added:
?
|
||
Don't think so, we have been having this issue on all our sites that have been upgraded to 3.5.1.
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/10255.
If you are using caching on your site, disable the page cache plugin. You should no longer have this issue. Let me know if that is the case for you.
Yes disabling cache fixes the issue.
edit: Not sure why disabling cache temporarily fixed it, but it wasn't the problem. The specific site with the issue had a mod_login override that needed to be updated.
A little update on this, using the current staging codebase, I can no longer reproduce this so it looks to me fixed for the next release.
Please use the forum for support http://forum.joomla.org
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/10255.