entity_translation 7.x-1.0-beta6

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:

Vocabularies that are handled by Entity Translation are tracked in a variable named entity_translation_taxonomy. Terms translated via ET should be detected automatically and the related vocabularies should be automatically configured accordingly. However, if before this update you had empty vocabularies, or vocabularies without translated terms, but expected them to be translated through ET, these vocabularies must be enabled for ET translation in the vocabulary form. Alternatively you can manually populate the variable itself, see #2914339: update 7008 caught me unawares for an example.

This also introduces an interesting change for developers, as now a new API to set the active language is available. This can be exploited to implement entity translation workflows that do not rely on the regular form-based UI.

New features

#1661348: I18n Taxonomy integration

Other changes

#2849464: Add an API to set active language (API addition)
#2438615: New nodes are always created using LANGUAGE_NONE (only changed to the correct language during form submission)
#2746045: Entity Translation path scheme default for entities of type Block does not declare a path wildcard. The entities of type Block do not define a valid path scheme: it will not be possible to translate them.
#1172104: Improve description of the language fallback option

Bug fixes

#2820454: PHP notice when attaching single field with field_attach_form
#2826297: 'clone' is a reserved keyword introduced in PHP version 5.0 and cannot be invoked as a function
#2189567: Problems enabling and disabling translation on a field with revisions enabled
#2798721: Path scheme not initialized on delete translation confirmation form
#2215771: Undefined index: translate in EntityTranslationDefaultHandler->entityForm()
#1829636: "All languages" suffix not working nicely with multi-value fields
#2757601: entity_translation_update_7009() assumes i18n_taxonomy is enabled
#2734373: "entity_translation_update_7008" is broken when no term is translated
#2734301: Numeric value out of range: 1264 Out of range value for column 'i18n_mode'