Troubles with the "LG Multi Language" plugin!
Development and Programming
Moderator’s note: Moved to Plugins.
Hello! I want to use the plugin to commit the following code for a translation:
{exp:lg_ml:translate p="Welcome to my Site"}Leevi writes in the docu:
Language files are used by the {exp:lg_ml:translate} plugin to translate pieces of text such as category names, menu titles or page headings. The language file must be placed in your template_base_path/language folder in your ExpressionEngine installation and use the following naming convention: lang.your-language-abbreviation.php.
I created i file, similar to the example file, called lang.de.php (for german translation) and putted it into the laguage/english folder, but it didn’t work. I tried to set the template_base_path in the administration, but doing this kills the whole site if “saving templates to files” is not wanted.
What can i do to work with the translate plugin? Cheers, e.
What happens if you set the template_base_path and turn off the option to save templates as files?
Well, if i set the template_base_path and place the language file in there nothing happens. But if i set the template_base_path and create a additional directory called “language” to store the language files the whole page rendering stops, and the ee outopts just a white page with no content… i have no idea why this happens…
A white page usually means that the language file is broken or php has made a fatal error. Is there anything in your apache / php error logs?
My language File is the same as in your example. I took a look in the error log, but there is nothing…
Btw: Is it possible to translate Categorytitles? I can’t create custom fields in the Category management. So how can i manage to do this?
Leevi, another BIG problem appeared: i prepared the whole page for the usage with your plugin with the languages German(de) and English(en). German ist the standard language, so i replace every german phrase in code by
{exp:lg_ml:translate p="<german word>"}to get it running if we solved the problem with the not found language file.
Worked fine so far. But during the testing of other stuff I recogniced, that your addon tries to search for a english version of the page even if there is any address that ends with “en”. For example in:
http://www.example.org/animals/chickenthe addon thinks that “chicken” is is the english version of “chick”. Funny example, i know, but instead of
http://www.example.org/animals/chickenthe addon searches for
http://www.example.org/animals/chick/en. Is there anything I did wrong or is this a serious bug in the addon? If so, do you have a patch for me to fix this asap?
Thanks, e.