D
D
Dima2015-01-19 10:37:06
MODX
Dima, 2015-01-19 10:37:06

Multilanguage in modx?

You need to make a site on modx - there is no problem with this, since the engine is absolutely wonderful, flexible and everything. But here's the problem with making it multilingual.
The easiest option is to duplicate resources, for example, we created the avalon.html page in the ru/ subsection and then we make the de/avalon.html page. But this is easy for me, but not for the future owner of the site, for him it will be an unnecessary trouble. Therefore, it must be done kosherly.
Found three options:

  • MIGX Multilang
  • Babel
  • Xlexicon

The first one is cool, but in order to master it, you need to master MIGX, which is not easy, and there is not so much documentation. And if everything is clear with MIGX, then everything is complicated with MIGX Multilang. I upload pictures to the default directory, but the plugin adds ru or de - completely inappropriate here. How to add tv to translation? The documentation describes the very basics, but there is not much sense from them.
Babel and xlexicon - there's a problem with contexts.
Most importantly, the site needs a very simple one:
A directory.
An ordinary visitor can add data with pictures to the catalog, but they will be added to the catalog after moderation.
Catalog search.
Object/product page.
How is it easier to implement? Should I bother with MIGX Multilang any further? Or is it easier with Babel?

Answer the question

In order to leave comments, you need to log in

4 answer(s)
E
Evgeny Mikhalev, 2015-01-29
@neznae4ko

as an option (I would not bother and do so)
I would simply create tv en, into which I would shove the translation into English, into tv de - I would shove Deutsch.
I would make a snippet that the user agent looks at. Depending on the language of the user's browser, you can give the desired TV. and if you need to switch the language, then do something like site.com/page.html?lang=de
so if there is a lang variable, then we give the language that is in lang, if not, then the one that the browser reported. if it was not possible to recognize the browser language, then we give the default language. By the way, yes, site.com/page.html?lang=de with the help of simple rewrite rules turns into some kind of site.com/lang/de/page.html thread and search engines love it))

M
MirageFFF, 2017-05-10
@MirageFFF

Lingua is a great plugin.
Or localizator from our compatriot.
In the first one, you can manage additional fields.
In the second, only content and pagetilte and other standard fields.

S
Svetlana Osipova, 2017-11-06
@osipova

I understand that the question is outdated for the author of the topic, but maybe it will be useful to someone.
My task was a little more difficult - to make multi-site in the admin panel and multi-language on each site. How did I implement it (in this I admire the flexibility of MODX, because there was even a choice - how to do it)
Multi-domain is implemented through contexts - this is an internal feature of the system. But multisite through Xlexicon. It just adds field translations to each page and shows the correct translation depending on which language is selected by the user. And the templates and all plugins/snippets are used the same, service translations are stored in dictionaries - this is also a built-in MODX feature.

W
webartdp, 2020-11-26
@webartdp

"Babel and xlexicon - there is a problem with contexts"
I would not say that there are a lot of problems. I set up multilanguage always in conjunction with Babel + Contexts. It is very convenient to work with such a site in the future. Here is a detailed instruction on setting up contexts and creating multilingualism in general.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question