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.
This is the first release of Entity Translation that supports PHP 8.x, it contains no change with respect to 7.x-2.0-rc1. See the related release notes for more info.
This is the first major update RC for the stable release of Entity Translation.
The most important change introduced in this release is the support for PHP 7.4 and 8.0, both for the actual codebase as well as the accompanying tests.
This is the first release candidate for Entity Translation. It is expected to be very close to the first stable release. This includes a few bug fixes and documentation improvements and a new feature. An old BC layer was also removed, see below.
This is mainly a stabilization release after the changes introduced in beta6. However a few minor feature additions were merged, the most relevant of which is the new Drush command to upgrade nodes from the node translation approach: drush entity-translation-upgrade.
This release introduces a long overdue feature: proper integration with the Taxonomy translation module provided by the Internationalization suite (see #1661348: I18n Taxonomy integration). Now it is possible to configure which translation method should be used for each vocabulary:
This release fixes an XSS vulnerability in the Entity Translation UI page titles. Since Entity Translation has no stable release yet, it is not officially supported by the security team. The issue was managed in the s.d.o private queue but no Security Advisory is going to be created.
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.
This release includes a huge number of new features and requires core at least 7.15. Many parts of the module changed since alpha2, hence you should backup your site and test it carefully when upgrading to ensure everything is still working for you.
This features a totally revamped translation UI (see #1282018: Improve UX of language-aware entity forms for details), which is using a language-aware entity form instead of a separate translation form. This allows to deal cleanly with modules adding new elements to the various entity forms. As a consequence the entity info needed to provide ET integration has slightly changed, check entity_translation.api.php to see if you need to adjust your code. Moreover hook_translation_info() has gone in favor of plain hook_entity_info() (see #1114410: Replace hook_translation_info() with hook_entity_info() ).
To replicate the behavior of the translation form shipped with alpha2 a new set of (optional) permissions have been introduced, see the related section in the Entity Translation guide.