?
avatar karendunne
karendunne
27 Mar 2016

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. screen shot 2016-03-26 at 21 02 04
screen shot 2016-03-26 at 21 01 59
screen shot 2016-03-26 at 21 02 07screen shot 2016-03-26 at 21 02 10

Votes

# of Users Experiencing Issue
2/2
Average Importance Score
5.00

avatar karendunne karendunne - open - 27 Mar 2016
avatar franz-wohlkoenig
franz-wohlkoenig - comment - 27 Mar 2016

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)

avatar franz-wohlkoenig
franz-wohlkoenig - comment - 28 Mar 2016

Problem on AMM is found and successfully fixed (more on Forum).

avatar marktaylor46
marktaylor46 - comment - 30 Mar 2016

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.

avatar alexmarketaccess
alexmarketaccess - comment - 26 Apr 2016

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.

avatar andrepereiradasilva
andrepereiradasilva - comment - 27 Apr 2016

Confirmed happening also on latest staging.

To reproduce:
1. Go to com_modules options in the backend and set the frontend edit links as "Administrator"
image

  1. Go to global config and activate edit modules on frontend.
    image

  2. Go to frontend, login and try to edit a module.
    image

  3. Result:
    image

More details: the error comes from here https://github.com/joomla/joomla-cms/blob/staging/administrator/components/com_modules/controller.php#L69.

avatar andrepereiradasilva
andrepereiradasilva - comment - 27 Apr 2016

@dgt41 can you check?

avatar karendunne
karendunne - comment - 5 Jul 2016

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.

avatar ggppdk
ggppdk - comment - 5 Jul 2016

@karendunne
you may test this PR:

#10753

avatar brianteeman
brianteeman - comment - 4 Aug 2016

Closing this so we just have one conversation in one place and we have a PR for testing #10753

avatar brianteeman brianteeman - change - 4 Aug 2016
Status New Closed
Closed_Date 0000-00-00 00:00:00 2016-08-04 09:54:24
Closed_By brianteeman
avatar brianteeman brianteeman - close - 4 Aug 2016
avatar PhilETaylor
PhilETaylor - comment - 8 Jan 2017

Please close this as we have PR #13516 which ultimately resolves this with ease.

Add a Comment

Login with GitHub to post a comment