Contrib.social

Entity configuration form allows to enable translation without any translatable field

Open on Drupal.org →
Created on 19 July 2014, about 11 years ago
Updated 12 August 2025, 5 days ago

Follow-up to #2300347: Regression: checkbox to enable translation for users does not save →

Problem/Motivation

Steps to reproduce:
1. install Drupal8.
2. enable language and content_translation modules.
3. navigate to Administration -> Configuration -> People.
4. under "Language Settings", click the checkbox to enable translation.

Expected:
Check if there at least a field with translation option.

Actual:
Allows to save.

Proposed resolution

We got two options:

1. Do the validation in content_translation_form_language_content_settings_validate to display the translate field
2. Get ride of the field in entity config form, so that the only way to update will be admin/config/regional/content-language page.

Remaining tasks

User interface changes

Yes, depending on the solution we go with.

API changes

N/A

📌 Task
Status

Active

Version

11.0 🔥

Component

content_translation.module

Created by

🇬🇧United Kingdom vijaycs85 London, UK

Live updates comments and jobs are added and updated live.
  • 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.

  • Comment 5 days ago →
    🇺🇸United States smustgrave

    Closed [#issues] in favor of this one.

  • Comment 5 days ago →
    🇪🇸Spain penyaskito Seville 💃, Spain 🇪🇸, UTC+2 🇪🇺

    Seems that there's some agreement on #6, which I added to the issue summary.

    But as a 11 years older me, I remember lots of pain giving support to customers with hundreds of content types and hundreds of fields which had timeout issues, or POST request size issues on admin/config/regional/content-language. The workaround on that case was hacking the config files (not recommended for not-advanced users), or indicate to go to each content type and each field and mark the relevant checkbox.

    So I think content_translation_form_language_content_settings_validate is a much valid approach, and/or even having a config schema validation constraint for this.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024