[bug] Translation does not work for backend ?

[baijianpeng]

Today I downloaded the latest version 3.1 of ionFiles component from this forum. Then I made a Chinese language translation for it and tested it on my local server.

But I noticed that the backend of ionFiles are all in English language. It seems that my translation did not work at all.

I checked the file system and found that there is no language folder in the /administrator/components/com_ionfiles directory. Is this the reason?

Please fix this.

Thank you.

[Jordan]

There is no translations for the administrative side of the component simply because no one has ever made one. If you send me your languages files (attach them here) I'll add them to the next release.

[baijianpeng]

Ok, attached is the Chinese language translation for ionFiles version 3.1.

Hope you will improve this component further.

Thanks.

[baijianpeng]

Today I downloaded the latest ionFiles version 3.2 and tested it on my Joomla! 1.0.13 with the site language set as Simplified Chinese.

Even I uploaded my Chinese translations for ionFiles to the correct folder which containing the english.php language file, the backend of ionFiles still show me English face.

I tried to rename or remove the english language file of ionFiles, then I noticed that all those backend strings turned into untranslated variables. That means ionFiles WILL NOT read those backend language strings from the correct language file according to the site locale settings. It just use the english language file for backend all the time.

So I think you need to modify some code to let this component pick up the correct language file.

Thanks.

[Jordan]

I completely forgot to add your language file, I will put it in the next release. In the interim the solution to fix this is:

in admin.ionfiles.html.php on line 17 change from:

if (file_exists($mos_absolute_path.'/components/com_ionfiles/language/'.$mosConfig_lang.'.php')) { 

TO:

if (file_exists($mosConfig_absolute_path.'/components/com_ionfiles/language/'.$mosConfig_lang.'.php')) { 

My earlier statement about how this had not been coded in the backend was incorrect. This has been coded but the path variable was incorrect (above).

Please let me know if this fixes your problem.