Initial permission: Edit values

Hi!

I see that "edit values" permission is initiated as "allowed" for each group. This is not so much the Joomla way IMHO, and it would better in any case to simply put the public group as "Allowed" and let the others inherit. Even more when the fields by default are "allow any editor to change" instead of "use ACL"

For example, think of this:

Public
- Editor1
-- Publisher1
- Editor2
-- Publisher2

I want to have a field that only publishers can edit. To do that, Editor1 must have "soft deny". So Public must be "Soft deny" also. Now, I have to remove the initial permission for each one individually. Its not a big deal, but I think its better that way.

Hello

the idea is simple

if a user can edit the item, they can edit the fields by default,

1. this causes less confusion, e.g. imagine you a user-group edit privilege and they discover that they can not edit fields inside it,


2. if you need to disallow a field the go ahead do the particular field


-- remember the "edit-values" privilege is usable only if you have edit on a item/category

this default behaviour will not change unless a very good reason is given


Regards

That makes sense

But they already can edit, isn´it? because for most of fields, they start with selected "ignore acl permissions for the field"

And the point is, there is no need to put each group as "allowed". Thats what inheritance is for. As long as the "Public" group is allowed, the rest will inherit, and when its not that so, like my case, will be easier to tweak

My 2 cents

Hello

about parameter it was added for compatibility reason, plus ... it alerts user they limit edition of individual field,

also in 80%-90% of cases edit all fields is the desired behaviour

that is why we did the similar thing in recent revision for:

can-change categoty assignments ACL privilege

Well, I have seen it and is the same problem. The joomla way is using inheritance. This complicate the configuration (larger permissions group inherit from more limited permissions group, so the soft deny allow this) If by default all is allowed, I can´t forbid some permission without breaking groups that inherit from it (that can need that permission)

I don´t see it, what is the problem on using inheritance and Public as initial group?

Hello

i see, so you mean we should ONLY set to allow at top level

1. set Public to "ALLOW" (top level of heritage of GROUPs)
2. then all other Groups can be set to "NOT SET"

-- thus if you need to change behaviour you can go to Public and change it to "NOT SET" aka everything becomes Soft Deny


(nevertheless we will always have for default installation edit values to "Allow" for Public user group)