- Issue created by @vermario
- @vermario opened merge request.
- First commit to issue fork.
Automatically closed - issue fixed for 2 weeks with no activity.
When the module is installed, fields are created for all existing taxonomy vocabularies.
The field storage gets imported as configuration, then instances are created for each vocabulary.
Currently the storage has set "translatable"= false
This means that he field does not appear on the content translation form, and when editing a single field we don't see the checkbox to set the field translatable.
Having that field as translatable is not something that we want, but I suspect that doing it like this will cause issues with the configuration... seems that it's the reason that for example the paragraphs module goes to all the trouble of showing you a notice on that page that says that you shouldn't set the paragraph field as non translatable. Why didn't they just set translatable = false on the storage?
Possibly we could:
1. set translatable = true on the field storage that we import
2. display a similar warning?
3. add an update function to set the storage to translatable = false
I wonder though... should we set the translatable = true property only if the site has a translation module active? this area is not too clear to me.
Active
1.0
Code
Automatically closed - issue fixed for 2 weeks with no activity.