Follow up for #1498674: Refactor node properties to multilingual →
Some use cases do not support multilingual scenarios yet, as they would require a contextual information about the language to act on. Solving this was out of the scope of #1498674: Refactor node properties to multilingual → and should be done after performing the conversion to EFQ2 [#X], exploiting the upcoming #1810370: Entity Translation API improvements → .
In the previous issue, 1498674, in many cases contextual information about the language to filter on would have been needed, but such information is not available yet, so the queries were just adapted to use the entity language.
Add contextual information about languages in queries.
None.
TBD
Contextual information: some use cases do not support multilingual scenarios yet, as they would require a contextual information about the language to act on. Solving this is out of the scope of this issue and should be done when performing the conversion to EFQ2 exploiting the upcoming #1810370: Entity Translation API improvements → .
Postponed: needs info
11.0 🔥
(Drupal 8 Multilingual Initiative) is the tag used by the multilingual initiative to mark core issues (and some contributed module issues). For versions other than Drupal 8, use the i18n (Internationalization) tag on issues which involve or affect multilingual / multinational support. That is preferred over Translation.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Is this still relevant to a supported version of Drupal?
Since we need more information to move forward with this issue, I am setting the status to Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.
Thanks!
