Labels |
Added:
?
|
Hmm, that sounds like a broken asset relation or something. When I try it, it works as expected.
Are those fields "old" ones you created like a month ago? Or did you create field and fieldgroups just recently for that test? I ask because ACL was broken and got fixed with #13676 on 2017-01-22. If your fields are from that time, they may have broken ACL assets and you would need to recreate them.
I had to reinstall everything 3 days ago due to the strange Routing error... It´s all fresh :) I try if it happens only there...
The only ACL setting which matters (or at least should matter) in that context is the "Edit Custom Field Value" one. The others are used when it comes to creating or editing the field itself, not its value.
That should make testing a bit easier.
What does the calculated settings column show for the field?
Category | ⇒ | com_fields |
@coolcat-creations @Bakual keep this issue open?
Category | com_fields | ⇒ | ACL com_fields UI/UX |
Status | New | ⇒ | Discussion |
I couldn't replicate it, so I have no clue where that may come from.
I am closing this at this time as it has not been replicated. It can always be reopened if required
Status | Discussion | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-08-19 17:52:17 |
Closed_By | ⇒ | brianteeman |
They aren't set to "Denied". They are set to "Inherited". Which means it's still possible to set children (the fields) to "Allowed".
If you set the fieldgroup to "Denied", then the field can't be "Allowed" anymore.
That's how the ACL works.