Problem/Motivation

A website with only one language activated is really quite different from a website with multiple languages activated. After adding a language the next step is not known.

Proposed resolution

After activating multiple languages, tell the user what steps to take now in possibly activating extra modules and make settings to content types (and possibly more, but I don't know now)

Remaining tasks

TBD

User interface changes

Possibly: show extra (modal?) screen for administrators that activate a second language

API changes

TBD

Comments

YesCT’s picture

There is help on the languages module.

But here, the suggestion is to have a message displayed (or maybe use tour) after adding the second language, maybe pointing to that help would be fine.

tammo’s picture

After consultation with Gabor I now understand the following (please correct me if I am wrong):

  1. I you want a website in three languages, say: English, Dutch and Russian, you have to start installing in one of these languages
  2. the language you choose for installing the site, will become your "Default language"
  3. if your "default language" is English, you have to go to admin/modules and switch on "Language", if your "Default language" is not English, the module "Language" was switched on automagically.
  4. after installing the website, please go to admin/config/regional/language and choose the additional languages you need
  5. after installing multiple languages (or if you installed Drupal with one non-English language) by default the modules "Language" and "Interface Translation" are switched on, "Content translation" is not (see admin/modules)
  6. if you want only one user interface language, not being English, you have to leave the module "Interface Translation" switched on (if you switch it off, the user interface language will be English) and indicate the language for your user interface at: admin/config/regional/language/detection in the first block that says: "User interface language detection"
  7. take care: even if you switch off the module "Interface Translation", on the page admin/config/regional/language/detection the first block about "User interface language detection" will show up, even though it does nothing
  8. if you want content pages be translatable, you have to switch on the module "Content translation"
  9. after switching on the module "Content translation", you can (or actually "have to") change the settings per content type at (for example): admin/structure/types/manage/article
  10. and after that you go to the page at: admin/config/regional/content-language and indicate which fields need to be translatable.
  11. if you add fields to a content type later, during the procedure of defining the field you will be prompted if the field needs to be translatable
tammo’s picture

The text on the Language page could actually be depending on which other core modules are enabled.

At least the Language module is switched on, or else the user would not see this page (would she?)

For example:
===============================
Interface translation: off
Content translation: off

With multiple languages enabled, registered users may select their preferred language and authors can assign a specific language to content. The selection of what language is used to display page elements is made depending on the detection menthod settings in the Detection and Selection tab.

[show only if multiple languages are enabled]

Your default language is: [Default language]. If you want to change this, please visit the[link to admin/config/regional/settings]Regional Settings[/link] page

If you want the user interface to be available in multiple languages, please switch on the "Interface translation" module on the [link to module page]module page[/link].

If you want to have translatable content, please switch on the "Content translation" module on the [link to module page]module page[/link].
================================
Interface translation: on
Content translation: off

With multiple languages enabled, registered users may select their preferred language and authors can assign a specific language to content. The selection of what language is used to display page elements is made depending on the detection menthod settings in the Detection and Selection tab.

[show only if multiple languages are enabled]

Your default language is: [Default language]. If you want to change this, please visit the[link to admin/config/regional/settings]Regional Settings[/link] page

You can configure the interface language settings on the languages [link to admin/config/regional/language/detection]Detention and Selection[/link] page

If you want to have translatable content, please switch on the "Content translation" module on the [link to module page]module page[/link].

================================
Interface translation: off
Content translation: on

With multiple languages enabled, registered users may select their preferred language and authors can assign a specific language to content. The selection of what language is used to display page elements is made depending on the detection menthod settings in the Detection and Selection tab.

[show only if multiple languages are enabled]

Your default language is: [Default language]. If you want to change this, please visit the[link to admin/config/regional/settings]Regional Settings[/link] page

If you want the user interface to be available in multiple languages, please switch on the "Interface translation" module on the [link to module page]module page[/link].

Content translation configuration is switched on. You can make content types translatable through the settings in each content type and additionally at the [link to admin/config/regional/content-language]Content language settings[/link] page

================================
Interface translation: on
Content translation: on

With multiple languages enabled, registered users may select their preferred language and authors can assign a specific language to content. The selection of what language is used to display page elements is made depending on the detection menthod settings in the Detection and Selection tab.

[show only if multiple languages are enabled]

Your default language is: [Default language]. If you want to change this, please visit the[link to admin/config/regional/settings]Regional Settings[/link] page

You can configure the interface language settings on the languages [link to admin/config/regional/language/detection]Detention and Selection[/link] page

Content translation configuration is switched on. You can make content types translatable through the settings in each content type and additionally at the [link to admin/config/regional/content-language]Content language settings[/link] page

tammo’s picture

Also add the text (visible when multiple languages are enabled):

Reordering the languages here will reorder the languages as they are shown in the "language selection" widget when create/edit content.

dagmita’s picture

The idea is to create a tour in Drupal 8. It will start when a user is adding another language.

dagmita’s picture

Issue summary: View changes

clarify problem

jojonmaster’s picture

Issue summary: View changes

very good problem and solving, inspired!
i will do it to my website, thanks

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Status: Active » Postponed (maintainer needs more info)

This issue has not had any discussion in 8 years and there are no tasks listed in the Issue Summary.

One of the comments mentions creating a tour. There is an issue to remove tour from core, #3325445: [Policy] Remove tour module from core.

What is there to do here?

Since we need more information to move forward with this issue, I am setting the status at Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

tammo’s picture

I do not use Drupal anymore. Do what you think is good.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

Status: Postponed (maintainer needs more info) » Closed (outdated)

per 18+19