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
Have an app that I've just switched from using
resources/lang/en/messages.php type files to using a single
resources/lang/en.json file.
When I use .json files for translations the fallback_locale set in app.php is not being respected, I'm getting the key of the strings instead of the fallback locale translation string.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Laravel version 8.6.4
Php 8.0.10
Have an app that I've just switched from using
resources/lang/en/messages.php type files to using a single
resources/lang/en.json file.
When I use .json files for translations the fallback_locale set in app.php is not being respected, I'm getting the key of the strings instead of the fallback locale translation string.
Using pseudocode to describe the issue....
This is what you'd expect, the fallback translation because no lang/ru/messages.php exists.
You would expect 'hi there!' as this is the fallback translation language.
ANyone have any ideas? Is this a bug?
Beta Was this translation helpful? Give feedback.
All reactions