- Issue created by @tonypaulbarker
- 🇺🇸United States phenaproxima Massachusetts
What I suspect is happening here is that another one of the recipes in the starter's stack is applying core's basic_html recipe (which is necessary in many cases for default content). Since the starter doesn't use config actions to set up its extensions to basic_html, but instead ships it wholesale in the config directory, it gets ignored so as not to conflict with the already-existing config.
What needs to happen here is one of two things:
The starter (or some other recipe in its stack) needs to use config actions to alter the basic_html format from core.
The starter needs to ship a different format that has the needed changes - this is the approach being taken in 📌 Create a new text format/editor to replace core's Basic HTML Active . - 🇦🇺Australia pameeela
Is there a problem with 📌 Create a new text format/editor to replace core's Basic HTML Active ? Would love to get that merged ASAP since it fixes this and other issues. Should really get it in before beta.
- 🇬🇧United Kingdom tonypaulbarker Leeds
@pameeela @phenaproxima thank you. That seems like the right way forward! Issue 3486284 is a different framing of the same problem and we should put our efforts to getting that done - we can extend that with config actions too if we want - so I’ll close this as a duplicate.
