Okay. I think I have fixed it. At the same time, I have made it so that any template variables ending in _{langId} where {langId} is a language group id are tabbed - not just the standard tvs managed by YAMS as was previously the case.
I have checked that this works for a Pre-Evolution install, but I am looking for a volunteer to test it on Evolution. Just rename the file to remove the .txt extension, and replace your current assets/modules/yams/yams.mm_rules.inc.php file with it. Then reload a multilingual document to see if it works.
Thanks.
Have you had this working on a non-production site?
I have just tried my first install of YAMS on a site in production.
Please can you show me a screen-shot of the top part of the same screen, with the monolingual settings and currently active mode?
You’ll notice that unlike most examples I have seen so far, I am not putting my default language in a virtual /lang/ directory, I rather English to be on the root.
The set-up you are trying to use is not normally allowed. Each URL for each language must be unique. Currently your English URL probably conflicts with your monolingual URL. If you need to avoid the use of a root folder name for English, then I think you might be able to do that by explicitly specifying www.quitsmokingin10days.com as the server name for all the multilingual documents, and something like mono.www.quitsmokingin10days.com for your monolingual pages.
Not at the moment. I hope that it is because of a configuration error and not something else.
but do you have any idea why I’d be getting 404 errors ?
With regards to the tabbed document view, have you edited your ManagerManager plugin to tell it to look in the mm_rules chunk? Have you placed the the YAMS ManagerManager rules in the mm_rules chunk?
The configuration looks fine. I can’t see any reason why we shouldn’t be able work to get this working since it has been working fine on other sites. Please can you post up your .htaccess? Also, are you using any other plugins that might interfere with the URLs in any way? Have you tried clearing your cache, btw?
Now, about the 404 issues. I tried changing my english to /en/ just to get rid of the conflict you mention, but it still doesn’t work - this time I get a browser error about a redirect loop that will never end - yes, I have updated my .htaccess file with the new rules.
Also the whole monolingual / same language as multi-lingual issue seems a bit unintuitive to me. I realize it may reflect some programmatic logic, but from a usability POV, it seems counter intuitive (unless I totally miss the point).
In most cases, a website will have a "dominant" language, and that brings the majority of traffic. In all my previous experience, for instance, we always use / for english, and then either a subdomain or a subdirectory for additional languages.
With YAMS, this "conflict" between, in my case, the "monolingual English" and the "multilingual English" seems really unnecessary. If I already have an existing site in English, isn’t it more user friendly to use THAT as the English version, exactly as it currently functions, and YAMS to ADD to it with additional languages in the root of the user’s choosing?
maybe I am missing something here.
Just a note on monolingual documents and why I treat them as distinct from multilingual ones. Some people like myself use MODx to manage non-html resources, like CSS, javascript, RSS and XML files as well as HTML content. It is not always appropriate to tie them into a particular language or view them via a tabbed language interface. I wanted a way of treating them like normal MODx documents.
I agree with you on several points.
1. YAMS isn’t very intuitive at the moment. Better documentation and simplified module interface could help here I think.
2. From the point of view of migrating an existing site it is better if existing URLs don’t have to change. It is possible to achieve that currently, but only if the server name for monolingual pages is different - which I admit is not very nice.
I hope that the goal with be what you hint at in point one - to get rid of this distinction between the monolingual, and the multi-lingual of the same language - it is too messy for a tight solution (I don’t mean programmatically - I mean in terms of usability and potential crawling problems that can be introduced to the site).
So, I need to look at several things:
1. Is it really necessary to be able to identify whether a page is mono- or multi- lingual from the URL from a programmatic point of view? What problems would it cause if monolingual and default language versions of multilingual documents shared the same URL.
2. If it is necessary to identify monolingual documents via the URL, then would it be nicer if monolingual pages could be specified under a subdirectory, like mysite.com/mono?
In the meantime, we should be able to get you up and running with some sort of working install - perhaps even with the default language installed at the root. Just need to figure out what’s causing those redirection problems.
.)
I see. I also use MODx to manage css, javascript, rss, etc., so yes, I do see you point. Maybe you could base this on content type - then the issue would only extend beyond normal HTML to javascript documents, but it wouldn’t affect css, plain text and xml formats.
It is highly likely that this plugin will have to be customised or re-written to work with YAMS, since it will need to be taught about multilingual URLs. I’ll have a look. So far I have been able to make YAMS work with Wayfinder, Ditto, Jot and eForm without having to hack any of the core code of those snippets - so if we’re lucky I’ll be able to do the same here. If we’re unlucky, we’ll need to re-write the whole thing using YAMS api calls...
Can YAMS work with SEO Strict URLs in the future? (Only you can tell me that Smiley.)
Monolingual mono.domain.com Multilingual English - www.domain.com Russian - ru.domain.com Spanish - es.domain.com
ServerName www.domain.com ServerAlias ru.domain.com ServerAlias es.domain.com ServerAlias mono.domain.com
Okay. We’re on the right track now.
First of all, lets clear up some misunderstandings.
1. YAMS doesn’t introduce ANY duplicate content. Monolingual documents are available at one URL only. Multilingual documents are available in several languages - each with their own unique URL. Translated content doesn’t count as duplicate content as far as search engines are concerned.
.
# For full documentation and other suggested options, please see
# http://svn.modxcms.com/docs/display/MODx096/Friendly+URL+Solutions
# including for unexpected logouts in multi-server/cloud environments
Options +FollowSymlinks
RewriteEngine On
RewriteBase /
# Fix Apache internal dummy connections from breaking [(site_url)] cache
RewriteCond %{HTTP_USER_AGENT} ^.*internal\ dummy\ connection.*$ [NC]
RewriteRule .* - [F,L]
# Rewrite domain.com -> www.domain.com -- used with SEO Strict URLs plugin
#RewriteCond %{HTTP_HOST} .
#RewriteCond %{HTTP_HOST} !^example\.com [NC]
#RewriteRule (.*) http://example.com/$1 [R=301,L]
# Exclude /assets and /manager directories from rewrite rules
RewriteRule ^(manager|assets) - [L]
# For Friendly URLs
# RewriteCond %{REQUEST_FILENAME} !-f
# RewriteCond %{REQUEST_FILENAME} !-d
# RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]
# The Friendly URLs part from YAMS
RewriteCond ${REQUEST_FILENAME} !-f
RewriteCond ${REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?q=$1&yams_lang=en [L,QSA]
RewriteCond ${REQUEST_FILENAME} !-f
RewriteCond ${REQUEST_FILENAME} !-d
RewriteRule ^ru/(.*)$ index.php?q=$1&yams_lang=ru [L,QSA]
RewriteCond ${REQUEST_FILENAME} !-f
RewriteCond ${REQUEST_FILENAME} !-d
RewriteRule ^es/(.*)$ index.php?q=$1&yams_lang=es [L,QSA]
RewriteCond ${REQUEST_FILENAME} !-f
RewriteCond ${REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]
# end YAMS
# Reduce server overhead by enabling output compression if supported.
#php_flag zlib.output_compression On
#php_value zlib.output_compression_level 5
But yes, now I see that the mono documents redirect to the multilingual default, so there is no dup. content at all.
RewriteCond %{HTTP_HOST} ^mono\.quitsmokingin10days\.com$
Quote from: towerofbabel at Aug 12, 2009, 04:00 PM
But yes, now I see that the mono documents redirect to the multilingual default, so there is no dup. content at all.
Hmm. That’s not supposed to be how it works. The mono documents are not supposed to redirect anywhere. In your case, if you go to http://mono.quitsmokingin10days.com/somemonolingualdocumentalias, you should just stay there.
Your .htaccess doesn’t look quite right. You’re missing a line like
RewriteCond %{HTTP_HOST} ^mono\.quitsmokingin10days\.com$
Ahh. That’s because server name mode is not active. To activate it you need to specify all the server names explicitly. I don’t know if that’s documented correctly. I’ll check.
So please try setting all your multilingual server names all to www.quitsmokingin10days.com (leaving the mono one as mono.quitsmokingin10days.com), then update your .htaccess (the rules will have changed) and try again.