Project Config support

[michaelroper]

Hey team! Just wondering, is there anything on the roadmap for this plugin to support the Craft 3.1 Project Config feature, so that field settings and preset settings can be saved into the project.yaml file and synced between environments?

[michtio]

@samhibberd sorry to be demanding but could you priortise this? :)

It's very hard to work with, when you don't make the end-user access the settings, but you do make changes to the presets locally. Changes never get merged.

[evanwarner]

Yep, gotta bump the importance of this too. Project config saves the presetId chosen on a field, but the preset itself is not saved, so a staging/production environment won't have the preset after a deploy. The current solution is either allowing admin changes on an environment where I otherwise wouldn't, or manually copying the colorit_presets database records.

[sjcallender]

@samhibberd Any updates on this? Not having presets in the project config is a pain. Hoping the fact that this is a paid plugin encourages some attention to this!

If you don't want to maintain it, let me know and I might venture to put an offer to buy it from you all.

[proimage]

This is pretty important; just bit me in the rear on a project.

[patrikalienus]

Although I have very little hope of it happening since this thread is from Feb 2019; Please add project config support.

[patrikalienus]

I really need to version control this, so as a workaround until project config support is a reality - if ever - I merely copy/paste the entire settings column from each preset in the DB, to a text-file within the repo. It's not exactly elegant and doesn't merge with the next release ofc, but as long as the presets are already defined in the DB, pasting the value is easy enough.

[Michael-Paragonn]

Bump!