Support/Comments for migxMultiLang

On that topic, however, phpthumbof has been deprecated in favor of pthumb or phpthumbsup.

https://github.com/modxcms/phpthumbof/
https://forums.modx.com/thread/?thread=86703&page=1

Hi Bruno, I am actually using pThumb but the phpthumbof cache still seems to be being used?

Yes, pthumb uses the same names as phpthumbof for backwards compatibility. I've also run into problems with images and caching with migxMultiLang and haven't solved them yet.

I can’t say installing it is a walk in the park for casual modx users, but I just want to say that this plugin rocks!
One thing my client said that its layout isn’t very intuitive, and she preferred a “global language switch” instead of clicking so much, but I imagine it’s not an easy thing to do.
From my perspective this helps a lot
http://rtfm.modx.com/revolution/2.x/case-studies-and-tutorials/create-a-multilingual-website-with-migxmultilang
and is easier to understand than the github version although, latter gives a better example. I would love to see a more complex examples and/or few examples of how to use it, with newly created tv’s/chunk’s.

Quote from: blackflow at Feb 08, 2015, 08:54 AM

I can’t say installing it is a walk in the park for casual modx users

Agree! But anyway seems better way than babel/context/htaccess mess. Especially when i have need for five langs.

i'll try this approach instead of Babel. I guess here will be some question in near future

Nice work!

How to define default lang? I've set two langs - English(en) & Finnish(fi) and i want 'en' as a default. My cultureKey is set to 'en', but site root directs to 'fi'?

the plugin does autodetect the users language and switches to that language by default.
https://github.com/Bruno17/migxmultilang/blob/master/core/components/migxmultilang/elements/plugins/mml_initculture.plugin.php#L78

In other words, your browser preference settings will have an effect on which language is used in the beginning.

I now have MML set up on a dev site (2.2.15) using the tutorial in the docs. This site was already complete with several templates. The templates all use chunks, and most of the resource fields are in chunks that are called in each template. So, now that the template itself becomes a chunk (for the MML setup), I have chunks within chunks (chunk children), and it seems any resource field that is in a chunk child does not get switched to the current language. The resource fields are only translated if they are in the parent chunk (the one that used to be the template).

Does this sound right to you? Is there a way to get these fields to work in a second level chunk?

Edit: just read back through this thread and it seems the child chunks need to be called uncached if they have translations. Will try that now. [ed. note: lucy last edited this post 11 years, 7 months ago.]

Issues I am having:

1. Want to use the default resource fields for the default language and use the standard placeholders (longtitle instead of mml_longtitle). This works for pagetitle and longtitle, but not for content. Using +content in the template chunk, the secondary language (Portuguese) is translated, but the default language (English) is missing entirely. If I use +content immediately following by *content in the template, I get two instances of English content on the English page, and one instance of Portuguese content and one of English content on the Portuguese page. Solved: make sure the mmlCache snippet call has the property: &includeContent=`1`

2. How do I deal with the Wayfinder menu. It is not using the translated menutitles. I see I am supposed to use pdoMenu...? Is there an example somewhere?

3. Can I make the mml_content a richtext TV instead of text? Nothing happens when I edit the TV input type. Solved: Open the MIGX Languages Form Manager, click Edit Raw button, change the inputTVtype for content TV to richtext instead of textarea.

Thanks! [ed. note: lucy last edited this post 11 years, 6 months ago.]