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
{{ message }}
This repository was archived by the owner on Mar 29, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 29, 2026. It is now read-only.
The navigation group is not changing through the translation file #127
I noticed that the navigation group name file is being obtained through the configuration file, and not through the translation file... I think it must be a temporary change that was not corrected, because this way we cannot translate the term for multilingual panels.
I saw that the option "'navigation_sort' => 1" was added, which is very good, but I think the group name should continue through the translation file...
Hello, I see that you "broke" this in January when moving navigation_group to config.
Found a solution myself: if you want to use filament-logger translations, use this line in config 'navigation_group' => 'filament-logger::filament-logger.nav.group',
Maybe this should be commented out in config in case someone wants to use it or smth. Thanks!
Reacted by malle-pietje, Ivo Junior and Aston Dihor
yes @krestaml
This makes it more interesting because the change is only in the configuration file.
But I believe that this adjustment should be made by default in config file, because in my view a label should be linked to a translation parameter so that there are no problems in multilingual applications.
I noticed that the navigation group name file is being obtained through the configuration file, and not through the translation file... I think it must be a temporary change that was not corrected, because this way we cannot translate the term for multilingual panels.
I saw that the option "'navigation_sort' => 1" was added, which is very good, but I think the group name should continue through the translation file...
In this case the problem is in the method:
=> ..\filament-logger\src\Resources\ActivityResource.php
Which should be corrected to: