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.

We're retiring the forums!

The SilverStripe forums have passed their heyday. They'll stick around, but will be read only. We'd encourage you to get involved in the community via the following channels instead:

Archive /

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

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

Please developers assist, several problems, I'm trying to help.

Go to End

3 Posts   1475 Views


Community Member, 3 Posts

12 June 2008 at 11:02am

Hi folks, I want to help with the multilingual support of silverstripe, since this is very important to me. I can do a lot of work with _t() functions and also finish the spanish translation. Now to the problems.


<% _t('DRAFTS','Drafts') %>
<% _t('SENT','Sent Items') %>
<% _t('MAILLIST','Mailing List') %>

do not care about language files. I'm using es_ES locale, and this strings are not translated at all, and they are present in the language file. Even changing them in the en_US.php results in no change. The only way I can change them is changing them inside the .ss template. Why? I have the same problem with some strings in the svn version of the blog module.

I'm trying to complete the multilingual support adding _t() functions, and adding the new translation array to en_US and es_ES.php, but this doesn't let me go further. This things unmotivate me. PLEASE HELP.


Community Member, 3 Posts

12 June 2008 at 11:09am

Here are the language translations from es_ES.php and en_US.php inside cms/lang

$lang['es_ES']['']['DRAFTS'] = 'Borradores';
$lang['es_ES']['']['MAILLIST'] = 'Lista de correo';
$lang['es_ES']['']['SENT'] = 'Elementos enviados';

$lang['en_US']['']['DRAFTS'] = 'Drafts';
$lang['en_US']['']['SENT'] = 'Sent Items';
$lang['en_US']['']['MAILLIST'] = 'Mailing List';

If you modify any of them, nothing happens even after a ?flush=1.


Forum Moderator, 801 Posts

20 June 2008 at 12:12pm

SSViewer (the template parser) and the textcollector have different ideas on which namespace the entities should be found - an inconsistency in i18n core. i've created a ticket:

this took me nearly two hours to debug, phew... sorry i can't help more right now, its a pretty tricky thing to fix.