-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow default/required settings on multilingual ("Language") fields #4322
Comments
Backdrop has integrated some i18n features in core and is trying to add more. In my understanding, the goal is to integrate chosen i18n-like features to core and to improve them for Backdrop. The respective meta issue is #3369. I'd suggest to add this issue there. |
@indigoxela Yes, some of those fields look like what I am referring to. @olafgrabienski Thanks, I'll add this to the meta. |
Now we need to figure out a subset of the i18n settings, that should get into core. 😉
The other stuff of i18n per content type settings I hardly ever use. @laryn what do you think? |
@indigoxela I agree with the subset you propose. |
@laryn until we get more feedback to reach consensus here, you could test the contrib i18n_node module. It seems to work now. 😉 |
No time to give well-considered feedback the next two weeks. However, the proposed subset sounds good to me, too. |
Currently the "Language" field on multilingual-enabled content does not have a default when you create content. Should this field carry over the default language from the site configuration, preselecting the default? Or should there be settings on the field per content type, for example, to set a default for that type of content? It would be helpful to be able to specfiy whether this field is required or not as well.
The text was updated successfully, but these errors were encountered: