Cloning and tweaking instead of having to start from scratch is much easier for people.
This may be a step towards solving some of the UX issues discussed in #1519 too. Site admins seem to be using the "Full HTML" format as a go-to solution when content editors demand more. This is OK in general, but it creates false expectations that people will get a WYSIWYG etc.
If we provided an easy way for admins to clone the "Filtered HTML" format, then they would do that, and add buttons + allow additional HTML tags as required (which is what they should be doing).
GitHub Issue #:
4501
Recent comments
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Importing the staged config throws an error: another field with the same name already exists
Thanks, I have to go out now, I will try later on and report back
Importing the staged config throws an error: another field with the same name already exists
Hi Francis. Yes, what config do you have in staging for it? You might have configs like: field.field.field_video_embed field.instance.node.page....
Importing the staged config throws an error: another field with the same name already exists