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
Bug in dropdown translation #953
Comments
Could it be reverted? |
Oups, sorry you've done it already, didn't you? |
Yes i do the revert and now all is OK: list of dropdown is not translated but item in a dropdown is translated in an object (tested with many objects like statuses, itil categories...). |
OK for not doing the translation, I agree with you that when editing master data, we can edit them in default language. |
OK i do the same in master branch |
OK for you in master too? |
I've no time to test, but I trust yours, so it's ok for me |
tests ok for me, i close. |
Sounds like there is still an issue in current Adding a status using dropdowns is working fine, but displaying the list produces the following error:
There is no table named As a quick fix, I've done:
This is maybe not the way to go, but doing this, I can now see my statuses list and translate them. I'm pretty unsure what should be done here. |
Still working on this one... The |
A fix proposal: |
The proposed solution add the missing query parts; retrieve translated value from DB, but this is not used (in administration, listed values should be what is exactly stored in database). A better solution would be not to translate at all ; but as soon as we've got a I'm not able to understand in which case the original code should be used; and so if the proposal breaks something or not. I give up. |
Saying that... I had an idea and I think I've finally find a fix... |
Checked and merged |
http://forum.glpi-project.org/viewtopic.php?id=150158
Introduce by 1f0fcdc#diff-a801c52129f44d50ab6d1db9f049c4b7
Dropdown list is never translated (because only use by super-admin).
Only dropdown in item is translated
The text was updated successfully, but these errors were encountered: