?
avatar infograf768
infograf768
19 May 2016

A. On a legacy test site (updated since 1.6 to staging) the Administrator Group, when set to "Inherited" for "Administrator Login", calculates the settings to "Not Allowed" in Global Configuration (related to C.)

legacy
On a vanilla new staging site, it is fine at first:

global admin

B. On both legacy and vanilla staging, when displaying the permissions for a component (here com_content), the Calculated Setting displays a lock with Allowed (Super User) although it concerns Administrator and not a Super User. Also as the settings can be changed, the lock makes no sense.

compallowed

C. In the component Permissions, If I change "Access Administration Interface" to anything else than "Inherited", it changes OK to "Denied" or "Allowed", BUT there is no way to get it back to its former state by using "Inherited". It will always now display "Not Allowed" if using "Inherited". This could also explain the legacy test site result in Global Configuration Permissions (see A. where I may have changed default setting at one point).

notallowed

D. Let's create a new Group "TestGroup" with Administrator group as Parent.

newgroup

In Global Configuration, let's set the "Delete" field for this new group to "Denied"

testgroupdenied

I am expecting that, by default, the "Delete" permission for this new group in any component would be set to "Denied". This is not the case. Also tested with other fields than "Delete"

notdenied

avatar infograf768 infograf768 - open - 19 May 2016
avatar infograf768 infograf768 - change - 19 May 2016
Category ACL
avatar infograf768 infograf768 - change - 19 May 2016
The description was changed
avatar andrepereiradasilva
andrepereiradasilva - comment - 19 May 2016

A. On a legacy test site (updated since 1.6 to staging) the Administrator Group, when set to "Inherited" for "Administrator Login", calculates the settings to "Not Allowed" in Global Configuration (related to C.)

C. In the component Permissions, If I change "Access Administration Interface" to anything else than "Inherited", it changes OK to "Denied" or "Allowed", BUT there is no way to get it back to its former state by using "Inherited". It will always now display "Not Allowed" if using "Inherited". This could also explain the legacy test site result in Global Configuration Permissions (see A. where I may have changed default setting at one point).

I think it's the same issue as #10121

B. and D. i think are another issues,

avatar phproberto
phproberto - comment - 21 May 2016

Checking this now from jandbeyond bug squash session.


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

avatar infograf768
infograf768 - comment - 22 May 2016

????


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

avatar brianteeman brianteeman - change - 23 May 2016
Labels Added: ?
avatar andrepereiradasilva
andrepereiradasilva - comment - 31 May 2016

@brianteeman this aCL stuff should IMHO be a release-blocker

avatar brianteeman
brianteeman - comment - 31 May 2016

will take a look tomorrow

On 31 May 2016 at 22:40, andrepereiradasilva notifications@github.com
wrote:

@brianteeman https://github.com/brianteeman this aCL stuff should IMHO
be a release-blocker


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#10552 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ABPH8dleehkardubRu4iEHXzOqWP3I6wks5qHKrZgaJpZM4Ih_7e
.

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

avatar aschkenasy
aschkenasy - comment - 1 Jun 2016

for me this happens only with the administrator group which is automatically calculated as su?

avatar roland-d roland-d - change - 1 Jun 2016
Labels Added: ?
avatar roland-d roland-d - change - 1 Jun 2016
Milestone Added:
avatar brianteeman
brianteeman - comment - 10 Jun 2016

Can I close this Issue now as it looks like everything has been addressed in existing PR now?


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

avatar brianteeman brianteeman - change - 10 Jun 2016
Status New Information Required
avatar sovainfo
sovainfo - comment - 18 Jun 2016

Confirm B, C, D are solved in 3.6.0 Beta 2 (3.5.0->3.5.1->3.6.0.alpha->3.6.0 Beta 1->36.0 Beta2)

avatar andrepereiradasilva
andrepereiradasilva - comment - 18 Jun 2016

sovainfo see #10793

avatar infograf768 infograf768 - close - 19 Jun 2016
avatar infograf768 infograf768 - close - 19 Jun 2016
avatar wilsonge wilsonge - close - 19 Jun 2016
avatar infograf768 infograf768 - change - 19 Jun 2016
Status Information Required Closed
Closed_Date 0000-00-00 00:00:00 2016-06-19 06:09:18
Closed_By infograf768
avatar infograf768
infograf768 - comment - 19 Jun 2016

Closing this as it is solved by #10793

avatar wilsonge wilsonge - change - 7 Sep 2016
Labels Removed: ?

Add a Comment

Login with GitHub to post a comment