Currently in the D7 version of ET we have the capability of marking each translation as individually published or not and providing additional translation metadata. We may want to retain this feature also in D8.
We will add this metadata to any entity as additional multilingual properties. At the moment only nodes natively provide this kind of information, which will be multilingual as soon as #1498674: Refactor node properties to multilingual. The idea is that nodes override the default translation metadata values with their native multilingual metadata. In a follow-up we could explore the possibility of extending these metadata to any entity regardless of translation.
Define which strategy we want to implement.
- @catch requests more reviews
- Reach the RTBC status.
User interface changes
UI changes need to be described.
Are there API changes/additions that would affect module, install profile, and theme developers?
cut and pasted from et ui part 2 issue summary to preserve knowledge:
No matter what we decide for the previous point, we should consider whether we should make the publication status a property of the entity translations, and thus making it available for any entity type. Should we only map per-language statuses to entity translation statuses for entities that support that (in core only nodes) or remove the special-casing from nodes and make the status a generally available property, that any entity type can leverage, at least when dealing with translation?