- 🇺🇸United States smustgrave
Based on #11 this could still be an issue. Moving to active and tagging for IS and steps to reproduce
I can confirm that D10 as well:
1. I have nodes that are translatable, but not localized
2. I manage language via session
3. Opening node in non-localized language all labels are translated, but taxonomy field itself is no.I attached image to describe issue better:
1. Node is not translatable, but not localized, ie only id default language
2. Reviewing node by forcing language in URL or managing it via session results in same: label translated to target language, but fields with taxonomy reference displayed in default language, but not URL/Session language.Would be happy to pay for the fix if anyone would be intersted.
- 🇺🇦Ukraine pablo_pukha
I have reviewed the issue and worked on a patch.
The patch fixes this by check if formatter is entity reference. While this solution works for the reported issue, I am unsure if it covers all edge cases. Feedback on this would be greatly appreciated.
Please review the patch and let me know if there are any improvements or alternative approaches you’d suggest