9 juli, 2012
Multilingual module 2.0 for Silverstripe CMS 3.0
With Silverstripe 3.0, the Silverstripe platform enters an new era. It’s now faster, more efficient and with even better user experience. We are really impressed of how the people at Silverstripe Ltd are moving the platform further ahead. It’s simply the best version yet! But - with all that said - we still miss a nice way of doing multi languages. At least the way we want it to. We realized quickly that the Translatable module didn’t do the job. We needed a single dataobject to hold all the translations - not several duplicate dataobject for every translation.
We previously had the same issue with Silverstripe 2.4. We therefore released an open-source module called ”Multilingual module” that resolved the problem we had the way we wanted it to. We have now rewritten it for Silverstripe 3.0. It’s even faster, cleaner and easier to set up than the first version. We are now offering this new module it with a commercial licence. You can still use our Multilingual module for SS 2.4 for free, but you’ll have to upgrade it yourself to work with SS 3.0.
Features
- Full Silverstripe 3.0 Support
Rewritten for Silvertripe 3.0. Its faster and cleaner. - i18n support
All lang files work as expected on front end. You can even set the mappings between language and locales. - Multilingual module works for all objects.
Set multilingual fields for Pages, Dataobjects and SiteConfig. - Not all fields on a object need to be translated
Select what fields you want to be multilingual on your object. - Front site URLs starts with language code
Swedish, for instance uses /sv/ in front of your site URLs. The full swedish URL could for instance look like this: www.mysite.com/sv/about-us/contact - Option to translate the URLSegments for each language
This feature gives you a unique URL depending which language is active. The above URL could instead look like this: www.mysite.com/sv/om-oss/kontakt - Easy and powerful to use
When having a lot of dataobject relations this way of working with languages is - in our opinion - superior.
Price
Price for the module is € 195.00
You’ll receive the download link as soon as the payment is confirmed! The link contains the full source code for the module.
The License grants you, the Purchaser, a non-exclusive, non-transferrable right to make use of the work you acquire.

Thanks for some other excellent article. Where
else may just anybody get that type of info in such a perfect way of writing?
I have a presentation next week, and I am on the look for such
info.
Did you consider releasing your module with cheaper licensing? Frankly - 195 EUR is quite much for small sites - and for this reason we are considering to migrate our site to wordpress.
Hi,
Is it compatible with SilverStripe-cms-v3.0.5?
Thanks,
Muhammad Kamran
Is this module going to work and be supported in Silverstripe 3.1 as well?
Well, yes and no. We have a Multilingual Module for SS 2.4 that you could try. It’s free and you can find it here: https://github.com/kreationsbyran/multilingual
Hi! Pali! Yes, you can use it on as many sites you like.
Hello,
I am not sure about the licence. Am I allowed to use it on one project only? Or as many as my company will do?
Project = website created for my customer.
Do you offer an evaluation copy of this module? I’d like to try it out to see how it compares to translatable for our workflow.
Is it possible from the frontend to switch to the default language if the content isn’t translate into the selected language?
Of course!
Is it possible to have a corresponding language switcher on the website?
thanks in advance
Rico
Yeah, you are right. We agree! That’s why the module supports multilingual URLs. Sorry if it was not clear in the post. You can of course translate the URLs as well so it looks like your example.
For Search Engine Optimisation you should consider speaking URLs, and multi-lingual speaking URLs.
http://www.mysite.com/sv/about-us/contact
is therefore ”wrong”
it should be like
http://www.mysite.com/de/über-uns/kontakt
http://www.mysite.com/en/about-us/contact
etc.
no? Think about it. Test it.