- Issue created by @andreasderijcke
- Merge request !37Issue #3514678 Select terms to list by their own default language and current interface language. → (Open) created by andreasderijcke
A follow up on 🐛 Term translation errors and performance issues Active , as the SQL queries introduced there make some assumptions about what the 'default' language should be for the terms.
The default language of the system, is not necessary the default language set by the interface/content language negotiation and default language that can be set on translatable entities itself.
While multi-language setups with different content and interface language negotiations cause all kinds of problems (even in core), following suggestion might help out here.
Consider setup where
In this situation, _term_reference_tree_get_children() does not return any result for the top level terms, as there are neither in EN (default language) or FR (interface language).
Fetch the terms having default_language = 1 or having the interface language.
This will cause all terms in their original translation language to be present, and we replace them with their label in the interface language if present.
As far as I understand the changes done for 🐛 Term translation errors and performance issues Active , the widget options should be as before but with the performance increase intact.
I'm assuming it is indeed the intention of the module to present all available terms in the widget, regardless if they should be rendered in the frontend, as there are other modules to handle/alter translation fallback behaviour and/or permissions to block viewing 'untranslated' entities in content language content.
Active
2.0
Code