This release introduces storage changes to support revisionable translation metadata, that was introduced in #1046282: Make the module work with revisions. This feature is disabled by default on existing sites to avoid problems with the upgrade path, instead it is natively available on new installations. People upgrading from earlier versions are strongly encouraged to backup their site database before proceeding.

People wishing to enable revision support on existing sites will have to perform the upgrade of translation revision metadata manually by creating a record in the {entity_translation_revision} table for each available entity revision. Simply copying values from the {entity_translation} table and updating the revision ids to the current version should be enough. Once this process is complete revision support needs to be enabled by setting the entity_translation_revision_enabled variable to TRUE.

Be aware that enabling revision support on sites where data has not been manually migrated may cause translation metadata to be permanently lost or corrupted. See #2396103: [DATA LOSS] Translations deleted for details.

Alternatively in #2402247: Migrate translation for enable revision is available some unsupported code trying to automate the upgrade process. That code might be perfectly working but has not been "officially" tested so use it at your own risk.

New features

• Issue #1046282: Make the module work with revisions
• Issue #1605406: Expose translated field content to Views so that multiple language translations can be shown simultaneously
• Issue #1516202: Add a CTools access plugin for checking if a translation is available

Other changes

• Issue #2185523: Document that entity_translation_enabled_bundle() does not check whether the entity type is translatable
• Issue #2027513: Allow nested value for 'edit form' in hook_entity_info() (API addition)
• Issue #2073231: Rename entity_translation_form_language() to entity_translation_get_existing_language() (API change)
• Issue #1865244: Allow multiple translation handlers on the same form
• Issue #1866076: Add support for non-entity load tokens when declaring translations

Bug fixes

• Issue #2396103: [DATA LOSS] Translations deleted
• Issue #2218087: PHP Fatal error: Unsupported operand types in modules/field_ui/field_ui.admin.inc on line 477
• Issue #2396653: Fix validation handler for the entity language widget
• Issue #2395327: FATAL error when requesting an edit path for a non-existent entity
• Issue #2342787: Language widget submit handler runs on disabled entity types
• Issue #2389945: Tests don't pass when using different source than original node language
• Issue #2378195: Node edit notice when author of a translation is deleted
• Issue #2382713: entity_translation_update_7006 fails because of SQL error before variable_set('entity_translation_revision_enabled', FALSE); can run.
• Issue #2179183: Fatal error: Unsupported operand types in /entity_translation.module on line 188
• Issue #2160559: Warning because of empty value line 675
• Issue #2151503: Check for translation access for Add links
• Issue #2130091: Media edit dialog integration bug
• Issue #2065221: Static cache for handlers should key by $vid
• Issue #2072865: Only replace "delete" button with "delete translation", don't add one that doesn't exist
• Issue #2055491: Synced image fields cannot be emptied