[#8731] - Update from 3.4.5 to 3.4.6 to 3.4.7: error in backend: You are not permitted to use that link to directly access that page
- Duplicate Report
- 22 Dec 2015
- Medium
- Build: master
- # 8731
Running Joomla 3.4.6 on centos 7.2, httpd 2.4.6, mariadb 5.5.4. Upated from 3.4.5 via backend joomlaupdate. Applies to both backend templates isis and Hathor.
After successfully logging in and editing one article by clicking on the article title and afterwards clicking "Save & Close", trying to edit that article again by clicking on the title of that article leads to an error message "You are not permitted to use that link to directly access that page (#someid)".
Another attempt to click on the title for editing does simply reload the page, but does not open the editor and does not display the error message above. This behavior remains until logging out and logging in again.
Please note that selecting the article via the left side check box and then clicking on the edit button does work, even repeatedly.
Votes
It seems that the subsequent ignored clicks on the article title come from the GET request with responose status code 303 being cached by e.g. Chrome 47. The GET requests never reach the backend!
When disabling the Chrome cache (within developer tools network tab, check button "Disable cache") everything is working as expected.
Unfortunately or fortunately, which depends on your point of view, since approx. 14:30 CET suddenly everything started working again, without having done anything. I don't know what's going on here. Kind of spooky!
The issue was at first verified to be there by two colleagues of mine with Chrome 47 and 48 on Windows 7 and IE 11.
This morning i verified the issue on two fresh joomla installations, a 3.4.5 instance where the problem didn't show up and 3.4.6 instance where the issue was reliably present.
Today one colleague also verified that the problem is gone without changing anything.
I'm closing this issue, til we maybe can reproduce it again.
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2015-12-21 14:46:43 |
| Closed_By | ⇒ | level420 |
After update to 3.4.7 the behaviour is back.
To reproduce:
- Logout from backend if logged in
- Login again to the backend
- go to Content and click on an article title to edit
- on the edit page click "Save & Close"
- back on the article list click the same (important!) article title again
you'll get the message
Error
You are not permitted to use that link to directly access that page (#72).
on first click. For all consecutive clicks the article list simply reloads without displaying the error message again.
| Status | Closed | ⇒ | New |
| Closed_Date | 2015-12-21 14:46:43 | ⇒ | |
| Closed_By | level420 | ⇒ |
| Title |
|
||||||
This is a non-issue - clear your cache, logout, clear your cache and kill your session and then everything will be fine.
I updated a site to Joomla 3.4.7 => visit link => error
Signed out/login again => visit link => success
What's your session handler? Do you have any cache enabled?
I can not reproduce it on 3 completely different instances. It looks like a local problem on your Joomla! installation.
@PhilETaylor I've allready cleared all caches in joomla and the browser and explicitly deleted all cookies. Terminated all browser instances.
php version is 5.4.16 on centos (rhel) 7.2, which means that there are a lot of backported patches from higher versions.
brianteeman
- | Status | New | ⇒ | Duplicate Report |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2015-12-22 10:42:35 |
| Closed_By | ⇒ | infograf768 |
joomla-cms-bot
- 
See #8757
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/8731.
Set to "closed" on behalf of @infograf768 by The JTracker Application at issues.joomla.org/joomla-cms/8731
@level420, you are very right to keep this issue open. I first started working on this glitch in 2012 and can report today that it is still occurring. This relates to a 403 Forbidden error produced by code in this file: ./components/com_content/controller.php. The same code is in J2.5.x and J3.4.8. You can see my extensive research into the subject in this old bug tracker: http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=29000. See "John Calvert" and scroll down to see the whole story.
If this is related to caching, or proxies, or timing... that is no excuse... we need to determine why this is happening in the field and find a solution inside of Joomla so that it doesn't keep rearing it's ugly head. It's not browser specific. The key is that Joomla's response to whatever condition is causing this is not the appropriate one, which presently is just giving the user a mysterious and frustrating message. We actually don't know that the root cause of this has anything to do with caching, proxies, or timing... it could be an actual defect in Joomla's coding, which is precipitated by caching, proxies, timing, (fill in the blank).
My background: I have 10 years of experience working with Joomla, PHP programming, and server administration. Before that I was a system software engineer for over 20 years.
So, let's fix this thing!
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/8731.
This issue has been reopened here:
https://issues.joomla.org/tracker/joomla-cms/9013
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/8731.
| Labels |
Added:
?
|
||
I've removed the browser dependencies, as I'm not really sure about that.
May be related to #8689