About block visibility

With this module enabled, the paths for block visibility are a bit different. You have to use language prefixes for them.

I.e.

<mypath>

will be now:

*/<mypath> -- for all languages
en/<mypath> -- only for page in English
es/<mypath> -- only for page in Spanish
....

Note: <front> doesn't work with '*' so you'll need to define it for each language and the actual front page
en/<node>
es/<node>
...

Custom home page for each language

Set up your home page in administer>settings, i.e. 'home'
Define a path alias for each language page. I.e. 'es/home', 'en/home'....

Different primary/secondary links for each language

  1. Enable language dependent variables. The one needed for this is 'menu_primary_menu', and 'menu_secondary_menu' for secondary links.
  2. Create as many menus as languages in administer>menus.
  3. Set up the menu to be used for each language in administer>settings>menus. You will need to switch languages while on this page.

Comments

ywarnier’s picture

ywarnier commented

Custom home page is actually set in Administer -> Site configuration -> Site information, one of the last options

--
Yannick Warnier
Project leader, Chamilo LMS
http://beeznest.wordpress.com/author/ywarnier
https://flattr.com/profile/ywarnier

light-blue’s picture

light-blue commented

In case this wasn't entirely obvious to you, as it wasn't for me, when the author(s) write:
>"Custom home page for each language"
>Set up your home page in administer>settings, i.e. 'home'
>Define a path alias for each language page. I.e. 'es/home', 'en/home'....

This means:
1. navigate to admin/settings/site-information
2. set your default front page to home
3. create something that results in a page: new node, a view with a 'page view', panels page, etc.
4. set an alias to #3 via URL aliases (admin/build/path) or pathauto (in the collapsible field of "URL aliases" at node content creation time) to es/home (for spanish) or fr/home (for french)

light-blue’s picture

light-blue commented

Unfortunately, I couldn't make this work the way it was explained. I have posted an alternate method using panels2, views, and a single home page, with view nodes dynamically translating based on selected language (http://drupal.org/node/108117#comment-860000).

wiert’s picture

wiert commented

After setting 'menu_primary_menu' and 'menu_secundary_menu' as described above,
assign a menu to the primary and secundary menu on

administer -> menu -> settings tab.

Then go to

administer -> localization -> manage strings

to search the menuname and translate it in the languages you need.

The menu will be kept in one huge menustructure but on the edit tab of your page you only see the menuentries for the curent language which is great.