Cannot translate title of Basic Page node if other content types are not translatable

Created on 13 March 2014, over 10 years ago
Updated 31 May 2024, 6 months ago

This is not good. Specific to Basic Page node type, you cannot translate titles apparently. To reproduce:

a) Install with Standard install profile.

b) Turn on Content Translation module and its dependencies, like Language.

c) Add French and Spanish languages (or whatever language you want)

d) Go to admin/config/regional/content-language

e) Turn on "Content" as having custom settings, and enable translation for Basic Page content type. Make sure both Title and Body are checked as translatable.

f) Add a Basic Page node in English.

g) Try to translate it. You will see "Title (all languages)" on the title field, and if you save a translation, the new title will spill over into your English node.

Note: See comments #4, #5, and #7 for clarification. The problem is actually that the UI for setting up content language settings does not currently match the actual configuration. Field settings for translatable and not translatable are not currently on a per-bundle basis, although the UI shows them that way. So if you have one translatable and one non-translatable bundle (content type), the individual field translation might or might not work, depending on whether the shared title and body and other fields end up being set as "translatable" or not globally. This is being addressed on related issue #2143291: Clarify handling of field translatability

🐛 Bug report
Status

Fixed

Version

8.0 ⚰️

Component
Content translation 

Last updated about 9 hours ago

No maintainer
Created by

🇺🇸United States jhodgdon Spokane, WA, USA

Live updates comments and jobs are added and updated live.
  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

  • D8MI

    (Drupal 8 Multilingual Initiative) is the tag used by the multilingual initiative to mark core issues (and some contributed module issues). For versions other than Drupal 8, use the i18n (Internationalization) tag on issues which involve or affect multilingual / multinational support. That is preferred over Translation.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024