Field editability conditions #16805
Merged
Field editability conditions #16805
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[ci skip]
|
Safe to assume that the "visibility" of a field is still a prerequisite for editability, in the underlying controller? Say I were to POST directly to (It looks to me like fields must be visible and editable, now, to be picked up, due to the implicit I think our current documentation on read-only field inputs should cover this, but I will expand the list of circumstances that a field might be rendered in static mode. ✌️ |
|
@AugustMiller Correct, a field must be both visible and editable to accept POST changes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Groups the existing field layout element conditions into a fieldset labelled “Visibility Conditions”, and adds a new “Editability Conditions” fieldset below it for custom fields, with “Current User Condition”.
When a custom field has editability conditions, they will be matched against the current user. If the user isn’t a match, the field will be displayed statically (read-only).
Related issues