Module does not work on localizations other than english
clava - January 3, 2008 - 15:26
| Project: | Hotkey |
| Version: | 5.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
First of all I would like to thank you for the very useful module.
I have a multisite installation (Drupal 5.5). One site works in english, the others in german. On the english site the module works as expected. On the german sites not. I even can not save settings and the hotkeys don't work in the forms.
Do you have any idea?
#1
The module only works if the user sets the language in "/user/***/edit" under "Interface language settings" to English.
#2
#3
I'm not familiar with any of Drupal's localization features, so you're going to have to help me out here to figure what's going on. If I had to guess, I'd imagine its because the button labels are ran through the translate function in Drupal whereas the default labels in the settings are not. In a recent commit, I'll be adding a change that translates the default values so that might do it.
As far as saving new key > Button label values in the settings form, is it not saving the new values you enter? I need a little more information to troubleshoot the problem.
#4
This is correct. As long as the user decides to have German as his standard language, he is not able to save new values. As soon as he change the language to English, everything work fine.
I will send you a private message with an account to test this behauvior on my testsite.
Thank you in advance
#5
After reviewing the code I see that I didn't use t() throughly through the module. I've done this throughout the .install & .module file. When the next release is rolled out, you should see these fixes implemented.
#6
#7
Automatically closed -- issue fixed for two weeks with no activity.