-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Module positions not always translated #12758
Comments
It can be a bit tricky because the positions are defined and (optionally) translated by the templates. Now each template may have a different name for the same |
Just seemed odd to me that we have the option to translate the positions On 5 November 2016 at 13:22, Thomas Hunziker [email protected]
Brian Teeman |
i actually made a poc for this (see andrepereiradasilva#99), but is as @Bakual says, will not be totally correct (altough i first find the position in the home template style which probably would cover more than 95% of cases). |
So long and farewell |
Steps to reproduce the issue
Go to the module manager and open the search filters
You will see that the list of positions include Position-7 and Position-8
Open a module and go to the list of available positions and you will see it is listed WITH its language string as well - which is much better and I am sure is the intended behaviour (why else have the strings in the template language file?
Scroll a bit further down that list and if you have a module published in Position-7 you will see it in the list of Active Positions but again without the translation
The same is true in lots of places - I just highlighted some obvious ones
Expected result
Actual result
System information (as much as possible)
Additional comments
The text was updated successfully, but these errors were encountered: