Quote from: MediaGuy at Aug 20, 2009, 12:16 PMIf the document is uncacheable, then the ditto call wont be cached, no matter whether it is specified with [! or [[. I can’t imagine why it wont work with both document and snippet call specified as uncacheable though. You’re right - it should still work.
Well, The document itself is uncacheable, but the Ditto call is cached and works! If I make the Ditto call uncached it stops working. Very strange, I don’t know what is causing this... normally it should not work this way!!
Optimally, you should have it set-up the other way around by the way. The document should be cacheable, but the snippet call should be set to uncacheable. I’m pretty sure that configuration works, because I have tested it in the past.
EDIT: Just to be sure we’re not talking at cross-purposes. It’s [!uncacheable!] and [[cacheable]]
That should be possible. It’s standard ’server name’ mode.
Specifically, I want:
http://www.quitsmokingin10days.com/ - ENGLISH
http://ru.quitsmokingin10days.com/ - RUSSIAN
http://es.quitsmokingin10days.com/ - SPANISH
I’m afraid I don’t understand your last point. Please can you provide an example of the kind of URL that doesn’t work?
Last week using a release candidate for 1.0.4, I followed your (PMS) advice and made mono.quitsmokingin10days.com my root for the monolingual version, and www.quitsmoking...., ru.quitsmoking....., and es.quitsmoking.... the roots for the multilingual versions.
This didn’t work for me. Specifically, all my relative paths for links, CSS, and so on in MODx became mono.quitsmoking..., making it unusable for me.
Quote from: towerofbabel at Aug 20, 2009, 04:25 PMThat should be possible. It’s standard ’server name’ mode.
Specifically, I want:
http://www.quitsmokingin10days.com/ - ENGLISH
http://ru.quitsmokingin10days.com/ - RUSSIAN
http://es.quitsmokingin10days.com/ - SPANISH
Quote from: towerofbabel at Aug 20, 2009, 04:25 PMI’m afraid I don’t understand your last point. Please can you provide an example of the kind of URL that doesn’t work?
Last week using a release candidate for 1.0.4, I followed your (PMS) advice and made mono.quitsmokingin10days.com my root for the monolingual version, and www.quitsmoking...., ru.quitsmoking....., and es.quitsmoking.... the roots for the multilingual versions.
This didn’t work for me. Specifically, all my relative paths for links, CSS, and so on in MODx became mono.quitsmoking..., making it unusable for me.
You should be able to safely set your base href tag to http://mono.quitsmoking.../. This will only affect your real files, like CSS etc. YAMS always outputs full absolute URLs for MODx documents and as a result they are not affected by the base meta tag. Hope that helps.
RewriteCond %{HTTP_HOST} ^www\.quitsmokingin10days\.com$
RewriteCond ${REQUEST_FILENAME} !-f
RewriteCond ${REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?q=$1&yams_lang=en [L,QSA]
RewriteCond %{HTTP_HOST} ^ru\.quitsmokingin10days\.com$
RewriteCond ${REQUEST_FILENAME} !-f
RewriteCond ${REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?q=$1&yams_lang=ru [L,QSA]
RewriteCond %{HTTP_HOST} ^es\.quitsmokingin10days\.com$
RewriteCond ${REQUEST_FILENAME} !-f
RewriteCond ${REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?q=$1&yams_lang=es [L,QSA]
RewriteCond %{HTTP_HOST} ^mono\.quitsmokingin10days\.com$
RewriteCond ${REQUEST_FILENAME} !-f
RewriteCond ${REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]
So, I need to be using virtual aliases, not "real" subdomains.
Monolingual mono.domain.com Multilingual English - www.domain.com Russian - ru.domain.com Spanish - es.domain.com
Yes. That should work. Just use the server names above, set the root names to empty, and update your .htaccess. You’ll probably also need something like:
ServerName www.domain.com ServerAlias ru.domain.com ServerAlias es.domain.com ServerAlias mono.domain.com
in your virtual host block, if you are using that approach.
Let me know how you get on.
Phew! Glad we got there in the end. I need to build that advice on setting up the aliases into the docs and the .htaccess config that YAMS provides.
Now I am in business!
One caveat - this method only works when ALL templates in use are multi-lingual - otherwise, links to pages with non-multi templates go to the mono. domain, and the www. domain links for those pages obviously doesn’t work (it actually gives an infinite redirect loop). I need to get YAMS to manage all my templates anyway, but is that a bug or an oversight?