If you have a field on one content type, you can easily add it to another content type using the 'Add existing field' option. This is great, and the fact that they can have different settings is cool too (e.g. 'field_image' on a post can save to 'files/blog' and be a large size, while the same field on a client content type can save to 'files/clients' and be a smaller size).
However, there are times when it's necessary to have the same settings for a field across all content types where its used (e.g. an ID number with certain min/max values, a postal address restricted to the site's country, etc.).
In this case, it'd be nice not have to manually copy over all the settings each time a field is added to a new content type. I'd therefore like to suggest a way whereby settings from another content type can be copied over with a field. These can then be changed for the new content type if necessary (i.e. nothing needs to change database-wise), but it prevents the same settings needing to be copied over manually.
I'm not sure how to implement this or what the UI/UX would look/act like, but thought to put the idea out there...
Recent comments
Ruby Text can be a bit of a hassle to edit... Yes, I can imagine that. No idea, how an editor dialog (or whatever) for easier editing of those should look like - in terms of...
Specific tags to work in CKEditor 5
"why are these tags only relevant for admins?" I'm allowing the editor as well. That being said, Ruby Text can be a bit of a hassle to edit... easy to accidentally delete a tag or part of a...
Specific tags to work in CKEditor 5
Out of curiosity: why are these tags only relevant for admins? Don't "regular" editors on that site also need them under circumstances? Yes, the editors play nicely, no problem to...
Specific tags to work in CKEditor 5