search

joomla / joomla-cms

Home of the Joomla! Content Management System
https://www.joomla.org
GNU General Public License v2.0
4.76k stars 3.65k forks source link

Error after update to Joomla 3.4.7 You are not permitted to use that link to directly access that page (#xx) #8757

Closed revers28 closed 8 years ago

revers28 commented 8 years ago

Steps to reproduce the issue

Update to joomla 3.4.7 Go to the view of the articles in the backend Try to edit an article in the backend bij click on title.

Expected result

You can edit the article

Actual result

You are not permitted to use that link to directly access that page (#xx)

Same issue when you go to templates

Steps to reproduce the issue

Update to joomla 3.4.7 Go to manage/templates in the backend Click on one of the templates.

Expected result

Acces to the template

Actual result

You are not permitted to use that link to directly access that page (#xx)

System information (as much as possible)

PHP gebouwd op Linux v34011.2is.nl 3.13.0-042stab108.2 #1 SMP Thu Sep 17 11:38:20 MSK 2015 x86_64 Database versie 5.5.46-MariaDB-1~trusty Database collatie utf8_general_ci PHP versie 5.5.9-1ubuntu4.14 Webserver Apache WebServer naar PHP interface cgi-fcgi Joomla! versie Joomla! 3.4.7 Stable [ Ember ] 21-December-2015 16:00 GMT Joomla! Platform versie Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT Gebruikersagent Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36

Additional comments

ggppdk commented 8 years ago

i will

PhilETaylor commented 8 years ago

actually I can add it to #9035

tehribo commented 8 years ago

I have the problem when Cache is set to "ON - Progressive caching" When OFF - I can open the article

gwsdesk commented 8 years ago

To what Joomla version you upgraded? To Joomla 3.4.7 as per title of this post? IF that is the case upgrade to Joomla 3.5.0 since providing advise is a) on the forums and not here and b) not effective on outdated software versions

Leo

On 3/30/2016 1:41 AM, tehribo wrote:

I have the problem when Cache is set to "ON - Progressive caching"

— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/joomla/joomla-cms/issues/8757#issuecomment-203043362

dig814 commented 8 years ago

I can confirm this still happens in Joomla 3.5.1. A workaround is to check the box next to the item and click "edit" This will et you in even when clicking the title does not.

edocif commented 8 years ago

Confirmed as well. Been an ongoing issue followed all steps when in a single session you can click the title of an article once, if you save & close or Cancel and try to click on the article title again you get the "You are not permitted to use that link to directly access that page (#97)." (or what ever ID you are trying to edit.)

edocif commented 8 years ago

found the issue to be in Akeeba Admin tools .htaccess maker. there is an option that is defaulted to "Yes" Set default expiration time to 1 hour.

Change that to No if you are getting the issue and it will disappear!

PhilETaylor commented 8 years ago

found the issue to be in Akeeba Admin tools .htaccess maker. there is an option that is defaulted to "Yes" Set default expiration time to 1 hour.

That is not the root issue. The root issue is that browsers cache the intermediate page redirect. Browsers are dumb. You make this caching worse by enabling features of Admin Tools to not expire for long times.

The correct solution to this issue is a complete rewrite of the way the edit page is loaded, and this needs to be able to be loaded without the intermediate page redirect being cached by browsers.

By as usual 'Aint nobody got time for that' amount of recoding

edthenet commented 8 years ago

So what about the issue 'You are not permitted to use that link to directly access that page' wich was the original question asked here. Will it be solved in the future, because i am using version 3.5.1 now and the problem still occurs?

durian808 commented 8 years ago

To my knowledge, this issue has yet to be fixed and has been present in Joomla since pre-historic times. You can read much detail about it here: https://issues.joomla.org/tracker/joomla-cms/9013. Here is my comment that gets to the crux of the matter: https://issues.joomla.org/tracker/joomla-cms/9013#event-125916. The current state of the testing/analysis is shown here: https://github.com/joomla/joomla-cms/pull/9035.

I, for one, would really like to see this fixed.

mbabker commented 8 years ago

An issue that isn't consistently reproducible and relies heavily on factors that make it difficult to damn near impossible to reproduce isn't going to get top priority or even fixed in a timely manner. Sure, people can test pull requests to make sure no regressions slip in, but if nobody except for one person on this entire GitHub repo can consistently manage to reproduce this random issue the odds of anyone ever truly deciding the issue is "fixed" are slim to none.

Not trying to attack anyone or say it's not annoying (hell, nobody's really dismissing it as not an issue), but so far the only somewhat viable reproduction instructions are "click a bunch of stuff really quickly until you manage to get the error".

durian808 commented 8 years ago

...so far the only somewhat viable reproduction instructions are "click a bunch of stuff really quickly until you manage to get the error".

Actually, that's what it seemed like initially, but I later ruled that out... it's not necessary to do it quickly.

It was easy to reproduce using SiteGround's demojoomla.org site, at the right time of the day (probably server load related). People argued that SiteGround was a crap environment, but I argued back that we are trying to reproduce an issue that is very difficult to reproduce in a non-crap environment, hence it's a good choice.

My comment of Feb. 6 explains:

@cpaschen we are trying to reproduce the problem and I have found that my SiteGround demo is a reliable way to do that. People are seeing this error in a variety of environments, but it is often very difficult to reproduce and therefor very difficult to test and try potential fixes. Both myself and @PhilETaylor have seen the issue come up recently on our client's servers. The one I observed was in the Rackspace cloud. Anyway, we are trying to flush it out and test it, not avoid it.

PhilETaylor commented 8 years ago

I have spent days and days on this before.

There are THREE different issues to resolve.

When I get time, I will document/fix all three - fixing one doesn't fix the problem.

The root problem is multi layered, involving session race conditions, server PHP processing and browser caching.

However at least one of the fixes has a MAJOR impact on API and Joomla internals, and so this is not a quick, simple, or pretty fix.

durian808 commented 8 years ago

Thank you @PhilETaylor. I'll try to get my SiteGround testing going again, w/ specific instructions to reproduce.

uglyeoin commented 8 years ago

Just to chip in. I get this error all the time. Exactly like the video. It seems to me to occur more frequently if you save and close an article and then try to go back into the same one again.

ggppdk commented 8 years ago

@uglyeoin

It seems to me to occur more frequently if you save and close an article and then try to go back into the same one again.

  • you have not mentioned if you have checked the case, that was explained above, and i will repeat below

if you get this repeatedly for an article / record, that you already edited and closed once,

Most usual reason for browser caching the 1st request is because your web-server was configured to send "cache-this" HTTP headers

PhilETaylor commented 8 years ago

Caching is only 1 part of this bug, but yes its a major part and can be further (negatively) effected by crazy/good .htaccess rules and web server configurations.

Hurmeli commented 8 years ago

I'm consistently running into this issue at least on couple of our clients Joomla installations. My personal fix was simply to stop using Chrome as it's the only browser the bug happens on (for me). I'm now using backend from Firefox instead.

Also sometime around Joomla 3.6 patch at least one site started exhibiting this behavior that hadn't done it before. Of course the reason might also be new version of Chrome rather than the Joomla update.

If it's any use to post System Information from Joomla, just ask.

This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/8757.

normdouglas commented 8 years ago

I have spent days and days on this before. There are THREE different issues to resolve. When I get time, I will document/fix all three - fixing one doesn't fix the problem. However at least one of the fixes has a MAJOR impact on API and Joomla internals, and so this is not a quick, simple, or pretty fix.

Hi Phil, sorry to drag this up... just wondering if there was any further movement on this?

durian808 commented 8 years ago

I will document/fix all three

I like the sound of that! More power to @normdouglas. Can we take a collection $$$ and stoke the fire?

normdouglas commented 8 years ago

For clarity, I'm not suggesting I've fixed it or have a fix... rather referencing some @PhilETaylor mentioned earlier.

ridgerobinson commented 7 years ago

Hello everyone...I have read through the forums, and understand this is a large problem at it's root. I am very much able to reproduce the same issue with the clear steps of opening an article/module, and then closing it and then re-opening the same one. A logout does provide a solution for re-opening it once, but then issue pops up again. Additionally, having cache disabled on my Chrome DevTools does solve the problem...but obviously can't expect my clients to do that!

I have just upgraded today to Joomla 3.6.5. Anyone have any update of at least a good temporary solution?

gwsdesk commented 7 years ago

Hello Ridge, This is not a support platform. This list is to communicate improvements to the Joomla CMS and systems.

Your question belongs on the forums so post on the forums in "general" to get support

Thanks

Leo Lammerink MD GWS-Global Web Services Ltd Member J-CMS Release Team

On 1/4/2017 9:44 PM, Ridge Robinson wrote:

Hello everyone...I have read through the forums, and understand this is a large problem at it's root. I am very much able to reproduce the same issue with the clear steps of opening an article/module, and then closing it and then re-opening the same one. A logout does provide a solution for re-opening it once, but then issue pops up again. Additionally, having cache disabled on my Chrome DevTools does solve the problem...but obviously can't expect my clients to do that!

I have just upgraded today to Joomla 3.6.5. Anyone have any update of at least a good temporary solution?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/joomla/joomla-cms/issues/8757#issuecomment-270386792, or mute the thread https://github.com/notifications/unsubscribe-auth/AHzLNqmOf-0q9Pgm4llrNzZnloDWhV3eks5rO7BfgaJpZM4G5yG2.

ridgerobinson commented 7 years ago

I was trying to help the movement of this issue, by confirming that the issue is still an issue with the latest Joomla version of 3.6.5.

I felt like I was keeping in tone with the rest of the forum on this page...really just wanted to see if anyone had found a good solution to this issue, which is an issue that needs to be improved on to the Joomla CMS and systems.

gwsdesk commented 7 years ago

It is not an issue that has been confirmed on the Issue Tracker https://issues.joomla.org/ nor in the JBS (Joomla Bug Squad so this place is not the correct location to file support. If you consider this a bug feel free to post an Issue on the tracker with link provided?

Leo

On 1/4/2017 9:59 PM, Ridge Robinson wrote:

I was trying to help the movement of this issue, by confirming that the issue is still an issue with the latest Joomla version of 3.6.5.

I felt like I was keeping in tone with the rest of the forum on this page...really just wanted to see if anyone had found a good solution to this issue, which is an issue that needs to be improved on to the Joomla CMS and systems.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/joomla/joomla-cms/issues/8757#issuecomment-270390455, or mute the thread https://github.com/notifications/unsubscribe-auth/AHzLNtz0ig4KmASf0A524EyHSt4evHz-ks5rO7PFgaJpZM4G5yG2.