Re: YAMS: Yet Another Multilingual Solution

After I clicked update, this happened:

Associated template variable <strong>pagetitle_en</strong> with template number 3 .
Associated template variable <strong>pagetitle_nl</strong> with template number 3 .
Associated template variable <strong>longtitle_en</strong> with template number 3 .
Associated template variable <strong>longtitle_nl</strong> with template number 3 .
Associated template variable <strong>description_en</strong> with template number 3 .
Associated template variable <strong>description_nl</strong> with template number 3 .
Associated template variable <strong>introtext_en</strong> with template number 3 .
Associated template variable <strong>introtext_nl</strong> with template number 3 .
Associated template variable <strong>menutitle_en</strong> with template number 3 .
Associated template variable <strong>menutitle_nl</strong> with template number 3 .
Associated template variable <strong>content_en</strong> with template number 3 .

And now they do appear for Dutch and English. However, not yet for German and French. But I guess I’ll try to recreate those language settings first, just to see what happens

Thanks!
Associated template variable <strong>content_nl</strong> with template number 3 .


EDIT:
OK, I simply had to activate the languages in question. It’s all done, I’m ready to go. However, 1 question arose: the default content fields etc. are all still editable. What language should go there?

Quote from: noes at Aug 27, 2009, 04:01 AM

After I clicked update, this happened:
...
And now they do appear for Dutch and English. However, not yet for German and French. But I guess I’ll try to recreate those language settings first, just to see what happens

The update problems you encountered were probably just a result of your yams.config.inc.php file not being editable previously. I hope that was the case anyway. If anyone else encounters update problems, please let me know.


Quote from: noes at Aug 27, 2009, 04:01 AM

EDIT:
OK, I simply had to activate the languages in question. It’s all done, I’m ready to go. However, 1 question arose: the default content fields etc. are all still editable. What language should go there?

They are redundant now. You can hide them. The setting is here: YAMS > Other Params > Hide Redundant Fields > Hide Fields

Great! Thank you for your time and dedication, thumbs up! Keep up the good work!

noes

Hi,
Thanks for a great module! It’s much better then making directory for each language

And now a question...

How can I output list of languages except the current?
e.g there are languages - EN, RU
At (En) version there should be link on language RU "Поменять на Русский"
At (Ru) version - link "Switch to English"

Thanks.

Quote from: Wild at Aug 28, 2009, 01:32 PM

Hi,
Thanks for a great module! It’s much better then making directory for each language

And now a question...

How can I output list of languages except the current?
e.g there are languages - EN, RU
At (En) version there should be link on language RU "Поменять на Русский"
At (Ru) version - link "Switch to English"

Thanks.

Hi, Wild Strike

The module is YAMS tab "Language Settings"
section "Select Language Text" changed "Select language" on "Switch to", and for the Russian language has changed in "Поменять на". Then create the following chunks
"list_current": <li class="yams_lang_(yams_id) yams_current">(yams_choose) (yams_name)</li>
"list_repeat": <li class="yams_lang_(yams_id)"><a href="(yams_docr)" lang="(yams_tag)" xml:lang="(yams_tag)" dir="(yams_dir)" title="(yams_name_in_(yams_id+))">(yams_choose) (yams_name)</a></li>
"list_after": </ul>
"list_before": <ul>

In the template, make a call chunk [[YAMS? &get=`list` &aftertpl=`list_after` &beforetpl=`list_before` &currenttpl=`list_current` &repeattpl=`list_repeat`]]

good luck

@jonimant
Thanks for idea! I needed it a bit different because current Language should hide and I just didn’t used chunk "list_current" from your example and left empty &currenttpl=`` in YAMS call.



and It’s worked

Are there any instructions for getting xml sitemaps to work with YAMS?

I used to use the Sitemaps snippet, but it is not supported by YAMS.

So, I thought to build my sitemaps with ditto, but the tutorials I know of use template "blank", and YAMS needs a template in order to assign across languages...

I actually want three separate sitemaps - one per language.

Thinking along - I guess I’ll encounter the same problem with my RSS feeds - "blank" templates. There too I’d like feeds per language.

Any suggestions on how to tackle this?

And another set of issues:

I have almost finished my site with YAMS now, it will go live with traffic in the next week or so.

However, I have some lingering worries, and I am not sure they come back to YAMS, but perhaps they do.


I commented earlier in this thread that I am noticing slow page loads at times. This continues. I have 15+ MODx sites across 3 different dreamhost servers, and I do not have this on any of them. The only new code on this install is YAMS.

Just one particular question about this PMS - because I have server name ON and root name OFF - do you think anything about this set up (which by the looks of it, I am the only one here using server name ON) could be causing this?

Further, I have noticed weird caching issues. I can’t explain them.

Yesterday’s one was the weirdest - I received a cached page on my spanish subdomain homepage (es.quitsmokingin10days.com) with a get statement my programmer wrote for me when we where setting up YAMS. It just printed something like "lang = es" so we could see that YAMS was working. Now, I got rid of this code from the page over a week ago now, and I have completely different content there. But, I was delivered this page yesterday!

I also had some pages (again, on my es.quitsmokingin10days.com and ru.quitsmokingin10days.com) load from cache with partial content - the complete <head></head> and around half the <body></body> missing.

I fixed these last issues by clearing cache in MODx.

PMS, I *know* this behavior sounds really weird, and is quite possibly not related to YAMS. But, I am still checking with you anyway. I am also taling to dreamhost about server issues. One thing I DID notice on the server is that my Server Alias domains (mono.quitsmokingin10days.com ; es.quitsmokingin10days.com ; ru.quitsmokingin10days.com) all have mod_security locked on, even though I don;t use it on the www. original domain.

ANY thoughts would be helpful.

I am using 1.0.5 beta of YAMS.

Hi All.

Sorry for not responding sooner to the recent posts. I normally check my email for alerts about updates to this thread, but for some reason I haven’t received any since the 27th. I was surprised that it had been so quiet!

Quote from: towerofbabel at Aug 30, 2009, 08:17 AM

Are there any instructions for getting xml sitemaps to work with YAMS?

Yes. Some step by step sitemap instructions are available.

EDIT: The instructions above are for creating a single sitemap. To create one for each language, use the same approach but don’t use the repeat syntax. Instead make your sitemap.xml template multilingual and place one ditto call in each content field.

@towerofbabel

The effects of YAMS on page loads times are as described in point 3 in the linked post. I don’t think the particular mode being used makes any difference to efficiency. I have started making a fairly major update to YAMS parsing designed at fixing many issues people have identified - efficiency included. I was hoping to get this finished this bank holiday weekend and although I have made reasonable progress, I haven’t been able to dedicate as much time to it as I was hoping. One of the issues I have already fixed is this requirement that the requirement that the monolingual URL is somehow unique. In the next version it will be possible to have, for example:

monolingual: http://mysite.com/
multilingual (default): http://mysite.com/
multilingual (other): http://mysite.com/other/ or http://other.mysite.com/

With regards to the caching issue, this is the first time such a problem has been reported. At this time I can’t rule out the possibility that its YAMS related. It’s difficult to fix a bug without being able to reproduce it, so if you get the opportunity to tie down the problem to a particular document or combination of settings or combination of snippet calls, then please let me know so that I can investigate. One thing to pay particular attention to is unexpected interaction with other plugins or snippets. Sorry I can’t be much more specific than that at the moment.