Integration with other contributed modules
Here are some notes about integration with other contributed modules. This about configuration and integration with other modules to use i18n features, but not about compatibility problems. If you have any issue about compatibility with other modules, please file a feature request on the issue tracker.
CCK
The Synchronization module works also for CCK fields.
There's no support (yet) for translating single fields into different languages.
Context
The i18n blocks module is not compatible with context. It won't break your site but just one of the modules will be able to handle the block selection. Change module weights so the one running later is the one handling the blocks.
Pathauto
AFAIK Pathauto module plays nice with i18n module. In addition to that, there are some features added into i18n module to provide different path templates for nodes depending on language.
Note: this won't work for bulk pathauto operations
- Add pathauto variables to language dependent variables in settings file, like:
- Set up different patterns for each node type/language on pathauto settings page (Like other variables, switch interface to set values for each language...)
- Play!
$conf['i18n_variables'] = array(
..............
'pathauto_node_pattern', // General pattern for nodes
'pathauto_node_blog_pattern', // Pattern for blog nodes
'pathauto_node_story_pattern' // Pattern for story nodes
............
);Views
There's some limited support for views strings translation using the included Views Translation module. Currently it allows translation of views title, header, footer and field names.
This is an ongoing work and it is a known fact that i18n's views support is far from complete so better than posting (yet another, duplicate) "I want better Views integration" feature request, you can comment on the existing one, #64004: Integration of i18n and views.module = fix translatablity of views . Patches are welcomed though.
As node language is a core field in Drupal 6, filtering based on language is now supported by the views module itself so post any related issue to Views module.
translating views based on language
One way to allow a view to be filtered based on the chosen language is to add the following code to the default of the Node Translation: Language Argument.
Steps
Add the Node Translation Argument to your view
Under "Action to take if argument is not present: "Choose "Provide default argument"
Chose "Php code"
Insert the code below
global $language;return $language->language;
Now when you go to that page without an argument the chosen language is automatically inserted as an argument. THis of ocurse kills the display of language neutral nodes for that view.
I'm using Views2 to do this
There is another more simple
There is another more simple way with Views2:
- Enable the Views translation module
- Add a new filter to the view and choose from group i18n the i18n: Content negotiation
that's all.
The last solution works like
The last solution works like a charm! Thank you very much!
Prisonbreaker
Vacation Rentals in Rio de Janeiro: www.apartmentinrio.net