Forum posts to 'Website Authors'

Re: Support for multilingual content

Andrey Zhuravlev — Thu, 07 Feb 2008 12:12:17 +1300

> I couldn't go back to English in the little drop-down at the lower-left corner

I encountered the same problem. When choosing English in the drop-down menu sometimes the site-tree does not refresh. Occasionally (can't figure out why) an Ajax error is occured when clicking "save&publish" the translation and the links in the site-tree stop to react. You have to refresh to go normal state. Though the content is saved and published properly.

Posted to: Support for multilingual content

Re: Support for multilingual content

Bernd Haug — Thu, 07 Feb 2008 09:39:37 +1300

Ingo - thanks for creating the ticket.

Regarding backtracking my steps, sorry but I don't remember. I would argue for the AJAX refresh being delayed though, as the translations were persisted correctly and were available shortly afterwards. I didn't try the immediate full reload at the time, though.

Posted to: Support for multilingual content

Re: Support for multilingual content

Ingo Schommer — Thu, 07 Feb 2008 09:15:03 +1300

> I couldn't go back to English in the little drop-down at the lower-left corner
did you create your translated page by the translation-tab ("create" button), or by clicking on an untranslated page in the sitetree? did you still have the problem after a full page-refresh? trying to figure out if the dropdown was properly populating by ajax, or if the language wasn't actually saved on the serverside

> The translation tool doesn't respect the Accept-Language
interesting, didn't know about this header - i've added a ticket: http://open.silverstripe.com/ticket/2231

Posted to: Support for multilingual content

Re: Support for multilingual content

Bernd Haug — Tue, 05 Feb 2008 10:12:40 +1300

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!

Posted to: Support for multilingual content

Re: Support for multilingual content

Sigurd Magnusson — Wed, 05 Dec 2007 10:17:32 +1300

konfjuzd; turn devmode on to see your error.

Posted to: Support for multilingual content

Re: Support for multilingual content

Henk Poley — Fri, 30 Nov 2007 00:08:56 +1300

Could somebody take a look at [url=http://open.silverstripe.com/ticket/1928]ticket #1928[/url]? Enabling i18n seemed to work fine. But I can't create translated pages.

Posted to: Support for multilingual content

Re: Support for multilingual content

Thu, 15 Nov 2007 22:40:45 +1300

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)

Posted to: Support for multilingual content

Re: Support for multilingual content

Andrew O'Neil — Thu, 15 Nov 2007 15:53:44 +1300

also it sounds like you have

<?phpi18n::enable()

instead of

<?php
i18n::enable()

Posted to: Support for multilingual content

Re: Support for multilingual content

Sigurd Magnusson — Thu, 15 Nov 2007 14:57:18 +1300

It requires SilverStripe 2.2+

Posted to: Support for multilingual content

Re: Support for multilingual content

Thu, 15 Nov 2007 10:57:10 +1300

hmm, nice but I fail on first line:

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

Posted to: Support for multilingual content