New answers tagged

1

AFAIK core's does not support (and could take a while to do so) keyed based translation (like Symfony or other do). Theres an idea queued but seems to fall on deaf ears.


1

After a bit of struggle and research, here is the approach taken - custom_module.install file - /** * Enable translation for workbench_reviewer field. * Implements hook_update_n. */ function hook_update_xxxx() { $entity_definition_update_manager = \Drupal::entityDefinitionUpdateManager(); $field_storage_definition_node = $...


1

The text of the submit button depends only on the translation settings of the status field. If the field "Publishing status" is not translatable for the content type, the button says "Save (all translations)". You can change the language settings for content types, taxonomy vocabularies, user profiles here: /admin/config/regional/content-language


-1

You can set it to “Translatable” at the “Entity” level and as such you need the following hook. hook_entity_base_field_info_alter It alters existing field definitions -like ones defined by other modules. There is also [hook_entity_base_field_info] to provide new field definitions https://api.drupal.org/api/drupal/core%21lib%21Drupal%21Core%21Entity%...


0

If you wont to show in views taxonomy terms, translated with entity_translate, try to use "Entity translation: Name" field instead "Taxonomy term: Name (translated)"


0

Your query is almost correct but you need to retrieve the entityTranslation in your entities, something like below for an article in English for example: entities { ...on NodeArticle { entityTranslation(language: EN) { entityLabel } } } See also here for a similar question and answer.


Top 50 recent answers are included