Closed (works as designed)
Project:
Drupal core
Version:
6.x-dev
Component:
language system
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
15 Oct 2008 at 22:12 UTC
Updated:
5 Aug 2009 at 18:59 UTC
Hi there,
I just freshly started a little site with only two languages with i18n. I would rather work it out with less modules, but I think this is not really easy...
So I wonder how I could get a translation switch. I know the difference between language switcher and translation switcher. But in my installation the translation switcher does not exist in the Blocks-Section at all. The language switcher works properly.
Anyone can help?
I already testet marking nearly all of the multilanguage features but the translation block wouldn't appear in the blocks-section.
Thanks.
Comments
Comment #1
konse commentedI'm the only one having this problem?
Any help out there?
Thx.
Comment #2
konse commentedSeems to me, that there is no more need of the translation block in Drupal 6.x
It is all set up through the language switcher block.
Comment #3
steff2009 commentedHello, I have Drupal 6.x and the translation block is not listed in Administer > Site builidng > Blocks, as you explain above that now everything is handled through the language switcher block.
In fact, the language switcher is there and works fine, allowing both to switch interface language and content language. However, at the bottom of each translated page, I see a clickable flag allowing to switch language as well.
I would like to remove this second "switcher" because I find it confusing for users, but I can't find it in the block list. How can disable it? Thank you.
Comment #4
brucepearson commentedI think there might be solution to this here - http://groups.drupal.org/node/16148
Comment #5
steff2009 commentedThank you, the group you redirected me to explains how to hide the footer flag in the CDD. However I need to correct myself: the language switcher works fine on every page except the front page.
To translate the front page I need to click on the footer flag appearing at the bottom of the page, because clicking the language switcher that I placed in the search box region won't work.
As a consequence, I must show the footer flag in the Home Page otherwise it cannot be translated. On the other side, I should hide the language switcher in the HP because it doesn't work.. but why doesn't it work?
Moreover, I don't want languages to be translated differently between HP and the rest of the site.
Comment #6
brucepearson commentedThis is what I have done to get the language switcher to work for the front page:
1) on the source (default) language front page set a URL alias to "home" for example.
2) on the site information page, /admin/settings/site-information, set the front page to "home"
3) for each page that is a translation of the home page set the URL alias to "home"
Now the language switcher should work.
also you can then get to the from page via http://yourdomain.com and http://yourdomain.com/es, etc.
you can see it working here:
http://drupal-translation.com
http://drupal-translation.com/de
http://drupal-translation.com/es
There is another way of doing this using multilingual variables that is a bit more complex. http://drupal.org/node/313272
Comment #7
steff2009 commentedThank you, but unfortunately URL alias links are not accepted in Drupal 6.x see http://drupal.org/node/65986 and Site configuration > front page too must always go to a real path.
I tried also the other option of reaching the HP through http://yourdomain.com, but the language switcher still does not work.
Is there another way to help (apart from using multilingual variables that sounds too complicated for me) ?
Cheers.
Comment #8
brucepearson commentedThe url alias method works fine for me when I set the url alias the same for the home page and each of its translations.
If I didn't do this it would give a page not found error when I used the language switch on the home page.
BTW - I'm using Drupal-6.6 and Drupal-6.9
Comment #9
steff2009 commentedI solved it like this:
1. I assigned "path prefix only" to the language settings (for me the the 1st language is IT and the second EN)
2. I assigned the prefix EN for English
3. I created the IT front page (node/16), chose language IT and left the menu link title empty in the primary links
4. I created the EN front page (node/17), chose language EN and left the menu link title empty in the primary links as well
5. In both the IT page and the EN page I checked "promoted to front page" in the publishing options
6. In Administer > Site building > Menus > Primary links, I created a menu item for "Home" and assigned its path to "front", parent item "primary links" and language "all languages"
7. In Site information, I put "node" as default front page
8. The language switcher now works fine: it changes the content from node/16 to node/17 based on selected language and the primary link "Home" always goes to the corresponding front page
Before doing this, I had two primary links going to Home, one for the IT version (node/16) and one for the EN version (node/17), but the language switcher wouldn't change content language on the front page (altough it did it correctly for other pages). To have it in EN I had to use the language link at the bottom of the page body. Now I was also able to hide the language link in the body by going to Administer > Site configuration > Languages > Multilingual system and selecting "Hide content translation links", leaving only the switcher.
Besides, I have a ddbock on my front page which wouldn't show on the EN version, because the theme foresees it only for the front page and it saw node/17 like a different page. Now I assigned "all languages" to the ddblock and it appears correctly also on the EN front page.
Cheers.
Comment #10
jose reyero commentedWhatever, this is Drupal core's Language switcher now.
It does some funny things like not showing up when there's no translations for the current node, but anyway, this is not an i18n issue now...
And anyway it just behaves as designed (and not by me btw) so please move the discussion to Drupal core queue.