awesome module! Thanks very much.
But unfortunately it does not support i18n strings. As i18n strings does not use the normal locale function to load the translation, it queries the DB directly.
So would be great to have support for i18n strings as well.

Comments

leksat’s picture

Status: Active » Needs review
StatusFileSize
new8.12 KB

Here is the patch providing the i18n support by replacing the i18n_string_textgroup_default class with custom implementation.

There is no way to alter i18n queries (see details in the code comments), so I just replaced original queries with custom ones. To see the difference between original and custom queries, take a look at this commit.

leksat’s picture

StatusFileSize
new4.79 KB

Whoops... wrong patch. Here is the correct one.

leksat’s picture

StatusFileSize
new7.93 KB

There were some issues with patch. The new patch also handles i18n string translation overview page and translation form (commit), and empty translation case (commit).

dasjo’s picture

Also see leksat's blog post for background info & explanations:
http://www.amazeelabs.com/en/blog/total-language-fallback

attiks’s picture

Status: Needs review » Fixed

Thanks all, merged

  • attiks committed 6902add on 7.x-2.x authored by Leksat
    Issue #2322883 by Leksat: Add support for i18n strings
    

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.