I found a need to be able to base the entity translation field on the user's context language as well as use the entity_translation table as the base table rather than the node table. This allows the autocomplete feature to look up nodes based on entity translation language rather than the base node language.

CommentFileSizeAuthor
#1 context_language_entity_translation_base_table-2233733-1.patch1.62 KBjwhitney64

Comments

jwhitney64’s picture

jwhitney64 commented
StatusFileSize
new context_language_entity_translation_base_table-2233733-1.patch1.62 KB
netsensei’s picture

netsensei commented
Status: Active » Needs work

Yes. Assuming you have the Entity Translation module enabled. The current version of the module does not support Entity Translation. Your patch directly queries the ET table. I think we need a bit more validation of the context (field translation v. entity translation, etc.) based on the entity/bundle settings here.

rcodina’s picture

rcodina
Primary language Catalan
Location Barcelona
commented
Related issues: +#2220563: Add language handling based on entity context language

Is 2220563 a duplicate of this one?

rcodina’s picture

rcodina
Primary language Catalan
Location Barcelona
commented
Priority: Normal » Major

I think support for Entity Translation is a priority. Patch on #1 doens't work for me: my parent entity is in english but only spanish taxonomies are listed.

rcodina’s picture

rcodina
Primary language Catalan
Location Barcelona
commented

What worked for me was taking original code and then remove this so "Select only nodes matching the parent\'s language" option takes effect.

&& $entity_info['translation']['locale'] == TRUE