This is a follow-up for #258785: Provide more flexible settings for initial language on content types
the UI / form has a language selector now, so this just inits the form element
it used to not have a form element, so this was the hard-wired language, but it now has a form element, so users can adjust as wishedit should have probably been done when we introduced the language form selector
Comment | File | Size | Author |
---|---|---|---|
#1 | 1809816-voc-add-1.patch | 845 bytes | andypost |
Comments
Comment #1
andypostSimple patch
Comment #2
Gábor HojtsyGood find! Before the patch the default for the drop down is the site default language on vocabularies. With this code clearly removed, what it is after the patch? (The code removed in the patch was added when langcode was introduced on taxonomy terms and vocabularies but the language selector UI on the entity form was not yet there.)
Comment #3
penyaskito#1987866: Convert taxonomy_vocabulary_add() to a new style controller removed that piece of code. The default for the drop down is the site default language on vocabularies still.
So I guess this is not a problem anymore.