Problem/Motivation

Any content type translation can be configured on admin/config/regional/content-language to "Show language selector on create and edit pages".

This
* allows the content author to select the original language on the create-page (which is a good thing)
* allows the content editor to change the original language on the edit page (which is quite confusing as users think they can translate this way), but only for the original-language item, not for translations

Proposed resolution

Weed the madness out by:
* Change the config option to "Show language selector on create (but not edit) pages"
* Provide a permission (or hidden BC config option) like "Show language selector also on edit pages"
* Add a upgrade path setting that permission / config option

(Feel free to object this radical approach)

Remaining tasks

Discuss, code, commit.

User interface changes

Change of a config option text.

API changes

Addition of a hidden BC config option.

Data model changes

None.

Comments

axel.rutz created an issue. See original summary.

geek-merlin’s picture

Here's the D7 Issue for reference.

geek-merlin’s picture

Title: Provide the option to lock the original content language » Lock the original content language

Adjusting title to sound more radical.

geek-merlin’s picture

Title: Lock the original content language » Lock the original content language by default
Issue summary: View changes

Added possible permission

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.

james.williams’s picture

kunalkursija’s picture

+1 for this functionality. As such behavior can cause issues like https://www.drupal.org/project/drupal/issues/2961670

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.

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.

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

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.