The first translation on the child item will be translated to the fallback language

[Sentence]

When listing an entity's childs, the first translation on the child item will be translated to the fallback language, the 2nd and 3rd in the list is using the current locale correctly.

Eg. the first one will be the fallback language, the rest will be the current locale:
{% for item in list %} {{ item.country.name }}<br/> {% endfor %}

If forcing the translation to the currenct locale with .translate(app.request.locale) it works

I'm using this bundle for 4-5 years now but got this issue twice only in many projects.

Any tips or suggestions?

[SVillette]

Same issue here, after some investigations, it seems to be linked to doctrine.orm.enable_lazy_ghost_objects: true.

[Sentence]

Yep, if i set it to false, it works, thanks a lot for the tip!

[SVillette]

Still an issue as setting this parameter to false is deprecated

[Sentence]

Sadly yes, but i'm using it currently in a Symfony 6.4.8 project (i'm trying to avoid 7 'til i can, since older/smaller bundles can conflict like this issue)

[bobvandevijver]

We hit this as well, but as we use our own translatable trait, it was easily fixable without submitting it here. The only thing you need is to override the getCurrentLocale and getDefaultLocale methods, and add the following:

    if ($this instanceof Proxy && !$this->__isInitialized()) {
        $this->__load();
    }

The issue is that non-mapped properties ($currentLocale and $defaultLocale) are marked as excluded by the lazy ghost as they are not mapped. Hitting these properties therefor no longer triggers database hydration, which causes the load event handler to not be run for the translatable if it wasn't fully loaded. Calling the load manually will trigger hydration and the load event listener, initialising these properties correctly.

I have created a PR as well: #767