The #1188388: Entity translation UI in core issue was committed with a considerable number of follow-ups planned. The main reasons for this were reducing the initial patch size to something not too painful to review and ensuring we had an MVP in before feature freeze to be able to refine it afterwards.

This metaissue has the goal to track all the most important ET improvements: a new issue queue component has been created but we have some issues that don't belong to it.

Node translation replacement

#1498674: Refactor node properties to multilingual
#1952062: Remove legacy translation module in favor of content translation
#1834250: Hide Content Translation module until we are able to remove it
#1833184: Find a consistent naming scheme for translation-related modules
#1952044: Migration path for legacy content translation module data

Usability improvements

#1810386: Create workflow to setup multilingual for entity types, bundles and fields
#1977784: Content language settings configuration page needs to determine what entities and bundles to include
#1807366: Make fields translatable by default when enabling translation on a bundle
#1807776: Support both simple and editorial workflows for translating entities
#2290101: UI telling you a field is shared across languages is way too subtle
#1832836: Discuss how to view original translation from translation form
#1498724: Introduce a #multilingual key (or similar) for form element
#1833022: Only display interface language detection options to customize more granularity
#1893568: Make each field instance have its own translatable property, instead of sharing translatable property with others.
#1833196: could not have interface in language A and create a translation from language B to language C
#1498880: Theme language switcher for seven theme
#1832870: Only show source translation column if there are 2 or more source languages (more than n/a and the original language).
#1831608: Show or hide the "Make field translatable" checkbox on the add field form depending on translatability
#1833104: Add a "translatable" column to Manage Fields
#1914800: Dropbutton width is smaller than longest item
#1807902: add hint to field collapsed global settings: GLOBAL SETTINGS: Number of values (1), Field translation (disabled)
#1807908: Autofill revision log with text that describes action like: German translation added or Spanish translation edited
#1807830: Improve UI by adding hint to add translation: source language collapsed field set
#2004878: config page title "Content language settings" misleading after translation is enabled

API improvements and code clean-up

#1810370: Entity Translation API improvements
#2019055: Switch from field-level language fallback to entity-level language fallback
#2004626: Make non-configurable field translation settings available in the content language settings
#2143291: Clarify handling of field translatability
#1498720: [meta] Make the entity storage system handle changes in the entity and field schema definitions
#1498660: Refactor taxonomy entity properties to multilingual
#1966436: Default *content* entity languages are not set for entities created with the API
#2230637: Create a Language field widget and the related formatter
#1810394: Site configuration with domain based language negotiation results in redirecting authenticated users to a different domain when accessing a content entity route for translation language different from the interface language
#1807800: Add status and authoring information as generic entity translation metadata
#1446382: Need a reliable way to determine if a specific bundle for an entity type is translatable (Fixed in D8)
#1916790: Convert translation metadata into regular entity fields
#2143729: Entity definitions miss a language entity key
#2155787: Deprecate ContentTranslationController::getTranslationAccess() in favor of a proper access controller
#1810350: Remove menu_* entity keys and replace them with entity links
#1831530: Entity translation UI in core (part 2)
#1810320: Remove EntityTranslationControllerInterface::getAccess() once have entity access
#1810330: Remove EntityTranslationControllerInterface::removeTranslation()
#1848904: Bundles cannot be specified in Entity Translation tests
#1968970: Standardize module-provided entity info documentation and clean-up the @EntityType annotation

Additional features

#1807692: Introduce a column synchronization capability and use it to translate alt and titles through the image field widget
#1807322: Filter comments taking into account the current content language

Entity Translation UI issues

Comments

plach’s picture

Issue summary: View changes

Updated issue summary.

plach’s picture

Issue summary: View changes

Updated issue summary.

plach’s picture

Issue summary: View changes

Updated issue summary.

plach’s picture

Component: translation.module » translation_entity.module
Issue tags: +D8MI, +language-content

Feel free to add new issues to the summary and/or announce them below, but let's try to limit the summary to important issues or ones that do not belong to the ET queue for easier tracking.

plach’s picture

Issue summary: View changes

Updated issue summary.

plach’s picture

Issue summary: View changes

Updated issue summary.

Gábor Hojtsy’s picture

YesCT’s picture

YesCT’s picture

YesCT’s picture

plach’s picture

Totally :)

plach’s picture

Issue summary: View changes

Updated issue summary.

YesCT’s picture

added #1914800: Dropbutton width is smaller than longest item to the issue summary.
(for example: "no translatable fields")

YesCT’s picture

Issue summary: View changes

Updated issue summary added issue for dropbutton cutting off long text: no translatable fields

plach’s picture

Issue summary: View changes

Updated issue summary.

plach’s picture

Issue summary: View changes

Updated issue summary.

plach’s picture

Issue summary: View changes

Updated issue summary.

YesCT’s picture

Issue summary: View changes

Updated issue summary.

YesCT’s picture

Issue summary: View changes

Updated issue summary, added older et ui follow-ups

plach’s picture

Issue summary: View changes

Updated issue summary

plach’s picture

Issue summary: View changes

Updated issue summary.

YesCT’s picture

#1938384: "Undefined property" error only after adding translations to existing content. was found by @craychee I'm pretty sure we came across that before, and now we have reliable steps to reproduce it.

YesCT’s picture

Issue summary: View changes

I was not sure if http://drupal.org/node/1938384 was a ui improvement or api.. it's really a bug. added the issue though.

plach’s picture

Issue summary: View changes

Updated issue summary.

plach’s picture

Issue summary: View changes

Updated issue summary.

YesCT’s picture

Issue summary: View changes

added ones from 1977784

plach’s picture

Issue summary: View changes

Updated issue summary

YesCT’s picture

Issue summary: View changes

add idea about renaming config page title

plach’s picture

Issue summary: View changes

Updated issue summary.

plach’s picture

Issue summary: View changes

Updated issue summary.

Gábor Hojtsy’s picture

Component: translation_entity.module » content_translation.module
Gábor Hojtsy’s picture

Issue summary: View changes

Updated issue summary.

plach’s picture

Issue summary: View changes

Updated issue summary.

plach’s picture

Issue summary: View changes

Updated issue summary.

plach’s picture

Issue summary: View changes

Updated issue summary.

plach’s picture

Issue summary: View changes

Updated issue summary.

plach’s picture

Issue summary: View changes

Updated issue summary.

plach’s picture

Issue summary: View changes
Parent issue: » #1188388: Entity translation UI in core
plach’s picture

Issue summary: View changes
plach’s picture

Issue summary: View changes
plach’s picture

Issue summary: View changes
plach’s picture

Issue summary: View changes
plach’s picture

Issue summary: View changes
plach’s picture

Issue summary: View changes
plach’s picture

Issue summary: View changes
plach’s picture

Issue summary: View changes
plach’s picture

Category: Task » Plan

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Ryan Weal’s picture

Priority: Normal » Major
Issue tags: +Migrate critical
mikeryan’s picture

Issue tags: -Migrate critical

@Ryan Weal - not clear why this was tagged "Migrate critical"? It's not actionable in itself, and has no open migration children. Better I think would be to tag any individual children of #2208401: [META] Multilingual migrations / i18n meta issue that we feel are critical and aren't already tagged.