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've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

Archive /

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

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

Support for multilingual content


Go to End


11 Posts   7971 Views

Avatar
konfjuzd

16 Posts

14 November 2007 at 10:37pm

How this works? any samples / tuts / docs?

Avatar
Fuzz10

Community Member, 791 Posts

15 November 2007 at 1:24am

Avatar
konfjuzd

16 Posts

15 November 2007 at 10:57am

hmm, nice but I fail on first line:

Fatal error: Class 'phpi18n' not found in /home/XXXX/XXXXX/_config.php on line 1
I put i18n::enable(); on top of config file.

Avatar
Sigurd

Forum Moderator, 628 Posts

15 November 2007 at 2:57pm

It requires SilverStripe 2.2+

Avatar
konfjuzd

16 Posts

15 November 2007 at 10:40pm

Edited: 15/11/2007 10:41pm

ok, it was <?phpi18n............

but now i have:

ERROR:
Error

The website server has not been able to respond to your request.

(and /db/build brings blank screen)

Avatar
Henk Poley

30 Posts

30 November 2007 at 12:08am

Could somebody take a look at ticket #1928? Enabling i18n seemed to work fine. But I can't create translated pages.

Avatar
Sigurd

Forum Moderator, 628 Posts

5 December 2007 at 10:17am

konfjuzd; turn devmode on to see your error.

Avatar
bernd

9 Posts

5 February 2008 at 10:12am

I just installed 2.2, and the translation feature seems to work (mostly) well.

2 little things I noticed:

* In the beginning (like, first 10 requests in the admin interface after creating a translation), I couldn't go back to English in the little drop-down at the lower-left corner, only French (my first translation language) was available. Now both are there and I can't reproduce the effect of only seeing the alternative language. That seems like a weird bug.

* The translation tool doesn't respect the Accept-Language. Switching with ?lang= works fine and sticks until it's reset again by the same means; but the first request is always served from the default language, not higher-priority languages set in the browser. I think the default until it's set with ?lang= should be according to the Accept-list of the user.

Thanks otherwise for the beautiful software, 2.2 seems much more polished and "production ready" in all regards than earlier releases. Great work!

Go to Top