-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error "You are not permitted to use that link to directly access that page" when using edit icon to access module from front end. Module editing set to administrator. #9615
Comments
I guess you don't use "Advanced Module Manager" (AMM) by NoNumbers. Had same issue with Core-Module-Manager and AMM if i used AMM 5.3.13. Using AMM 5.3.11 had not this Issue with Core-MM or AMM. Happened on Sites using Joomla!3.4.8/php5.6 or J3.5/php7 (Conversation on NoNumber-Forum) |
Problem on AMM is found and successfully fixed (more on Forum). |
I can confirm this issue too. I test with a brand new Joomla 3.5 clean installation (default english sample data) using Protostar template. The only thing I changed was in module manager options to change "edit module" from "site" to "administrator". As soon as you have logged into frontend and click to edit any module your will get the error message reported (whether or not you are logged into the backend). Regards, Mark. This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9615. |
Confirmed this is also happening with Joomla 3.5.1. I changed from Administrator to Site, and then I can edit modules in frontend. If I change to Administrator, and edit a module in frontend, I am redirected to backend and get the error messaged reported. |
Confirmed happening also on latest staging. To reproduce:
More details: the error comes from here https://github.com/joomla/joomla-cms/blob/staging/administrator/components/com_modules/controller.php#L69. |
@dgt41 can you check? |
is there a known timeline for this to be addressed? This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9615. |
@karendunne |
Closing this so we just have one conversation in one place and we have a PR for testing #10753 |
This comment was marked as abuse.
This comment was marked as abuse.
…13516) * Fix “You are not authorised to view this” when mod_expires enabled Closes #8731 Dec 18, 2015 Closes #8757 Dec 21, 2015 Closes #9013 Jan 28, 2016 Closes #9145 Feb 17, 2016 Closes #9615 Mar 26, 2016 Closes #10753 Jun 7, 2016 * code style * Unit test refactoring (cannot do it the old way as relative dynamic dates in headers) * Remove duplicate header output for charset * Better Unit Tests * More unit tests :) * Close after setting headers * Do not cache the response to this, its a redirect
Steps to reproduce the issue
Have module options set to edit module via administrator (see screen shot)
Login to front-end
Click on edit icon for a module (see screen shot)
This next step would normally take the user to an open module for editing (see last screen shot)
Instead, it takes the user to the list of modules and gives this error:
"Error. You are not permitted to use that link to directly access that page (#90)"
The (#90) would be which ever the module ID is. (see screen shot)
Expected result
To be taken directly to the module for editing, as if I had opened it from the administrator to begin with
Actual result
Leads to the module administrator page with the error highlighted in pink:
"Error. You are not permitted to use that link to directly access that page (#90)"
The (#90) would be which ever the module ID is.
System information (as much as possible)
Joomla 3.5
PHP 5.6, also tested in 5.5 with same result
Safari 6.1.6
Firefox 45.0.1
Opera 36.0
Chrome 49.0.2623.108
Additional comments
I have tried this on three installations now and the issue is consistent. All three installations were Joomla 3.5. My other sites that are running 3.4.8 work as expected, meaning that when I click on the edit icon it immediately opens the module for editing via the administrator.
The text was updated successfully, but these errors were encountered: