Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
An entity can be not enabled for translation but at the same time may be sharing translatable fields with a translatable entity type or bundle. In this case a change in the entity language is not handled because the entity translation handler is not instantiated and tied to the entity form.
Comment | File | Size | Author |
---|---|---|---|
#2 | et-disabled_translation-1890346-2.patch | 1.99 KB | plach |
#1 | et-disabled_translation-1890346-1.patch | 1.99 KB | plach |
Comments
Comment #1
plachHere is a patch performing only the language widget handling for untranslatable entities.
Comment #2
plachFixed typo.
Comment #3
plachComment #4
plachCommitted and pushed.
Comment #6
drzraf CreditAttribution: drzraf commentedI got an issue using latest 7.x which wasn't happening using beta2. I now come here after the result of the bissection blamed 33651f45.
The issue is:
entity translation
for a given bundle (type
== report)content translation
for a given bundle (type
== page)fr/node/1470/edit
(several other translations already exist)Result:
Guess:
The hunk providing:
elseif ($info = entity_translation_edit_form_info($form, $form_state))
may be missing an additional test as, in my case, it succeeds while it probably must not.
If I understood that part of the code, this makes
entity_translation
the handler, but I believe that should not happens here.Let me know if you need additional information.
Comment #7
plachI think I stumbled upon this as well, just forgot to open a new issue. Please open a new one and move #6 there as OP. Will meet you there :)
Comment #8
drzraf CreditAttribution: drzraf commenteddone with #1924088: Wrong form "language" value in case of content-translation enabled bundles