ContentEntityInterface::getTranslation() returns a new translation if the specified language is valid but there's no corresponding translation for it yet. This is not ideal, we should be creating new translations explicitly. Moreover this has also performance implications, since
ContentEntityInterface::addTranslation() is slow (see also ).
ContentEntityInterface::addTranslation() invocation from
- Figure out what's the desired behavior when
User interface changes
Data model changes
Beta phase evaluation
|Issue category||Bug because this can trigger unexpected behaviors.|
|Issue priority||Major because this has several implications: it makes the Entity Translation API more fragile, it may cause perfomance issues when listing multiple entities in multilingual environments and is also preventing us from finding a sane solution for.|
|Prioritized changes||The main goals of this issue are reducing API fragility and improving performance and security.|
|Disruption||Disruptive for contributed and custom modules leveraging the Entity Translation API in an improper way. Core fixes are mainly in tests.|
FAILED: [[SimpleTest]]: [PHP 5.5 MySQL] Unable to apply patch et-invalid_translation_exception-2090983-22.patch. Unable to apply patch. See the log in the details link for more information.
[ View ]