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 wished

it should have probably been done when we introduced the language form selector

CommentFileSizeAuthor
#1 1809816-voc-add-1.patch845 bytesandypost

Comments

andypost’s picture

andypost
he/him
Primary language Russian
commented
Status: Active » Needs review
Issue tags: +D8MI
StatusFileSize
new 1809816-voc-add-1.patch845 bytes

Simple patch

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Status: Needs review » Postponed (maintainer needs more info)

Good 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.)

penyaskito’s picture

penyaskito
he/him
Primary language Spanish
Location 🧑🏽‍🌾 Seville 💃 Andalusia, UTC+2 🇪🇺
commented
Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (won't fix)

#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.