[6.x] Add option for addons to opt-out of config layouts for settings#12869
Closed
duncanmcclean wants to merge 1 commit intomasterfrom
Closed
[6.x] Add option for addons to opt-out of config layouts for settings#12869duncanmcclean wants to merge 1 commit intomasterfrom
duncanmcclean wants to merge 1 commit intomasterfrom
Conversation
Member
|
This might be good to have, but the issue described in #12810 feels like a bug. The config field layout should only be applied to fields at the top level. |
Member
Author
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
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.
Addon Settings publish forms currently use the "config" (50 / 50) layout for displaying fields.
While we aim for all configuration & settings pages to use the config layout, this PR adds an option for addons to opt-out and use the "content" layout instead (the layout used on entries, terms, etc) if it better suits their use case:
Closes #12810