Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.


Our old forums are still available as a read-only archive.

Moderators: martimiz, Sean, biapar, Willr, Ingo, simon_w

Translation Problem


6 Posts   1826 Views


20 November 2007 at 11:04am 9 Posts


I'm trying to translate SilverStripe into Turkish and the translated string on my language isnt showing.. Still English is showing in some sections on the gui. I cannot exactly find the problem :S Could you please explain the problem for me?

here are the language sample language strings:

$lang['en_US']['']['PAGEVERSIONH'] = 'Page Version History';


$lang['tr_TR']['']['PAGEVERSIONH'] = 'Sayfa Sürüm Geçmişi';

Here are the sample screenshots:


23 November 2007 at 3:16am 9 Posts

so this is an end of life? :) doesnt any body has any ideas?


23 November 2007 at 3:43pm (Last edited: 23 November 2007 3:44pm), Forum Moderator, 628 Posts

This is a bug in SilverStripe.

I don't see you at so are you doing your turkish translation on your own, and not contributing it to the core package?


24 November 2007 at 10:19am 9 Posts

I cannot see the signup link, button on the site before today i got a mail and then i apply ;) but there is a problem: we've created language transations on the files and it looks like from the translation module, we need to translate it one by one.. is it possible to just upload the translated files and a php script gets the translated strings and set them as the translations on the working language? it would be nice..


24 November 2007 at 7:33pm Forum Moderator, 801 Posts

at the moment you can't upload /lang-files to the translationserver on your own, but feel free to send me the files and i'll try to import them into the translationserver-database (ingo at ourcompanyname dot com).

IMPORTANT: in case you copied your lang-file (e.g. pt_PT.php) from the master-file (en_US.php), you have to make sure you don't redefine priorities/context etc. each translated entity has to be a string, not an array - otherwise our fileparser goes nuts ;)


24 November 2007 at 9:08pm Community Member, 21 Posts

Oppps that was directed to me Ingo ;)

I got the message :)

Best regards,