You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because, currently it will use the explicitly specified locales or the request locale .
In every cases, Translator fallback is not working cause fallbackLocale is just not included in the return of route 'bazinga_jstranslation_js'.
As a workaround I have to include the fallbackLocale manually as mentioned here : #214 (comment) <script src="{{ url('bazinga_jstranslation_js',{"locales": app.request.locale ~ ",en"}) }}"></script>
Example:
Default locale : fr
Locale : it
Fallback : en
User was by default in FR, he switched in IT but there's a missing translation key 'app.country'. It should be loaded from EN translations but it's not.
The text was updated successfully, but these errors were encountered:
Hello,
I'm currently having some trouble with the fallback behaviour.
In this method, shouldn't the fallbackLocale be added to the default locales ?
BazingaJsTranslationBundle/Controller/Controller.php
Line 194 in 26d3793
Because, currently it will use the explicitly specified locales or the request locale .
In every cases, Translator fallback is not working cause fallbackLocale is just not included in the return of route 'bazinga_jstranslation_js'.
As a workaround I have to include the fallbackLocale manually as mentioned here : #214 (comment)
<script src="{{ url('bazinga_jstranslation_js',{"locales": app.request.locale ~ ",en"}) }}"></script>
Example:
User was by default in FR, he switched in IT but there's a missing translation key 'app.country'. It should be loaded from EN translations but it's not.
The text was updated successfully, but these errors were encountered: