Multilingual site in MODx

Since we are creating a webshop in MODx...we’re also thinking about making it Multilingual.

Putting that thought aside, i was wondering if MODx has ANY tools available in it’s core
for multi-language based websites aside from the lexicon. I mean dynamicly translated content
like resources...or webshop products etc.

Since i don’t like creating a translation system only for the webshop...and i’m unwilling to
believe MODx has not even the slightest support for multilingual sites???

Thanks in advance!

as of what i know, there is no core-function for multi-language-content.
a common way to go is to have duplicated content trees along seperate folders/contexts.

a way of using contexts (de,fr) to show up in a way like domain.com/de domain.com/fr has been described here.

I am really confused. I’m wondering what the train of thought goes behind the fact that there’s no multilingual support at all in the core.

There’s support for multiple sites, love that! Why not multiple languages? It’s what every reasonable CMS / framework has...why not MODx? I can’t imagine there haven’t been any discussions about it...(i mean wether it should be in the core or not).

What are the teams thoughts about leaving support for multiple languages entirely up to the developer?

I’m very curious

Because the vast majority of sites are not multi-language. The whole thinking behind MODx is to provide a basic core functionality that is easily built on with various plugins, modules and snippets to customize the core. Revolution is even more so.

Why should the dozens of sites I’ve built over the years carry all that extra code, when only three or four of them have wanted more than one language? Can you imagine what MODx would look like if it had every possible feature that everyone could want hard-coded into the core? I’ve worked with systems like that, and it’s a nightmare.

You are kinda misunderstanding what im saying. Im not saying EVERYTHING should be hardcoded. Im just saying language support should. Ive been building websites for quite some time now and ive needed multiple languages alot. I know its not the case with most of you american people that build sites mostly only in english, but from where im from its need alot.

I consider this core functionality, not extra functionality. I know the MODx filosofy and i totally agree. I just dont see that language support doesnt fit in. And i know tons of people that agree....so what you just said just doesnt seem like a valid point for me.

Just because they dont need everything in the core doesnt mean they dont need just this one feature...its requested alot in the forums here too.

My friend, everyone says that their pet feature should be hardcoded. You do know the story of the farmer and his son taking their donkey to market, right?

Haha no, but pls, do tell

First, make sure you’ve read this, which covers the dilemma very concisely: http://modxcms.com/forums/index.php/topic,43806.msg298361.html#msg298361

That said, we are certainly looking to add and improve i18n "features" in the core moving forward. However, I don’t think there will ever be a one-size-fits-all multi-lingual solution in the core of MODx. But then again, that’s why we’ve developed MODx Revolution to be so easily extensible; a one-click install multi-lingual Extra will surely be realized once we get past the public launch, and my hope is that several will appear that meet different i18n needs.

http://www.pagebypagebooks.com/Aesop/Aesops_Fables/The_Man_the_Boy_and_the_Donkey_p1.html

Thanks for your responses. Im aware of the current solutions offered.

I think well develop our own multilinual solution then

And i really enjoyed the story btw :-D