Skip to content
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

Open
laryn opened this issue Feb 27, 2020 · 7 comments
Open

Allow default/required settings on multilingual ("Language") fields #4322

laryn opened this issue Feb 27, 2020 · 7 comments

Comments

@laryn
Copy link
Contributor

laryn commented Feb 27, 2020

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.

Screen Shot 2020-02-27 at 3 38 12 PM

@indigoxela
Copy link
Member

I think, i18n module provides what you need (could provide - it has no stable release for B) .

Here's a screenshot of the Drupal version (the Backdrop version needs some help and loving care).
screenshot-d-i18n

Are these the settings you're missing?

@olafgrabienski
Copy link

Here's a screenshot of the [i18n] Drupal version (the Backdrop version needs some help and loving care).

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.

@laryn
Copy link
Contributor Author

laryn commented Feb 28, 2020

@indigoxela Yes, some of those fields look like what I am referring to.

@olafgrabienski Thanks, I'll add this to the meta.

@laryn laryn changed the title Defaults for Language field Allow default/required settings on multilingual ("Language") fields Feb 28, 2020
@indigoxela
Copy link
Member

indigoxela commented Feb 29, 2020

Now we need to figure out a subset of the i18n settings, that should get into core. 😉
Based on the settings I usually use that could be:

  • Set custom language as default for new content.
    • Current language
    • French (as example...)
    • Italian (as example...)
    • ...
  • Require language (Do not allow Language Neutral).

The other stuff of i18n per content type settings I hardly ever use.

@laryn what do you think?

@laryn
Copy link
Contributor Author

laryn commented Feb 29, 2020

@indigoxela I agree with the subset you propose.

@indigoxela
Copy link
Member

@laryn until we get more feedback to reach consensus here, you could test the contrib i18n_node module. It seems to work now. 😉

@olafgrabienski
Copy link

until we get more feedback to reach consensus here ...

No time to give well-considered feedback the next two weeks. However, the proposed subset sounds good to me, too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants