Using translation keys with double colon does not work #144
Unanswered
renepardon
asked this question in
Bugs
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi guys,
I import the translations like this:
"pages" in this case is a nwidard/laravel-modules module. The translations are located within the modules own resource directory. To access such a translation, I would usually use
__('pages::general.labels.pages_admin_languages')
where "pages" is the module and "general" the name of the file.If I change the group key to "general" only, without the "pages::" prefix, the translation gets loaded from DB when accessing it like this:
__('general.labels.pages_admin_languages')
. But we really need the namespace/prefix. What can we do here?Beta Was this translation helpful? Give feedback.
All reactions