While it's great that static and default variables are translatable, there was only one set of settings which should be in only one language. This is acceptable for a translated site, it's a real problem for a multilingual site. I did a lot of research and found a simple and flexible solution: use i18n API. I patched the module and thoroughly tested it and it works flawlessly on a i18n multilingual site and I see no reason why it wouldn't work if the base multilingual module was another as long as i18n is also installed. I included instructions in the patch that would help integrate the procedure on another version or even another module. I'm using singular while there's 2 of each because it's a copy of the same code, one for input and the other for output.

CommentFileSizeAuthor
i18n_translatable.patch1.96 KBdynv

Comments

john.oltman’s picture

Status: Needs review » Closed (won't fix)

Version 5.x is no longer supported. Please upgrade to version 6.x or 7.x and reopen the issue there if the problem still occurs in one of those releases.