Live conditional fields without autosave #14115
Merged
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
No longer dependent on autosaves
brandonkelly
changed the title
[ci skip]
brandonkelly
deleted the
feature/cms-1229-conditional-fields-wo-autosave
branch
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
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
Adds live conditional field support to all element editors, even if drafts/autosaves aren’t supported by the element type (or it’s been disabled via the
autosaveDraftsconfig setting).That includes full edit pages for assets, as well as editor slideouts for assets, tags, and users.
In Craft 5, full edit pages for users will also be included, as they now use the element editor.
Related issues