- Issue created by @dcimorra
Reported at the DrupalCamp 2023 talk in Seville
Because the module retrieves the fields as solr stores them and the language is hardcoded in the field name itself, we lose the translation support, forcing the developer to create different displays for each of the languages.
Enable module, add fields and configure a view.
Enable field patching with the entity, either internally or externally, so as not to lose translation support.
Investigate possible solutions, such as the possibility of including the external_entities module.
N/A
N/A
N/A
Active
2.0
Code