Open
Conversation
+ Added an option to choose whether to apply colors across all sites, or keep setting specific to each site. + Removed the translation select box. + Ensured the “site wide” changes don’t get modified when site specific changes are made.
|
Is this going to be reviewed and implemented @samhibberd ?? This is a must have feature. |
Contributor
|
Yes absolutely @michtio, field presets / settings might be getting a little restructure which needs to be considered carefully to ensure backwards compatibility, we will implement either way. Thanks for the pr @thejoshsmith. |
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.
Use Case
I wanted to be able to set field specific settings per site. I.e., it'd be great to create a bunch of presets (e.g. themes for each site), and toggle that preset on the same field.
What I did
Craft doesn't support multi-site field settings out of the box. The simplest approach I could think of was to simply store the site specific settings in an array key called "siteSettings", and direct Craft to load those ones when required, otherwise falling back to the default settings.
I added a toggle so users can choose whether their color settings will be propagated across all sites, or specific to each site.
I also removed the translation field, as I don't think it's relevant for this field type? (Correct me if I'm wrong!).
How to test
coloritfield and assign to a section(Note: I tested mine inside a matrix).