Can't get views.module and i18n to work together

Has anyone a clue about this?

Here is a temporary solution that makes this technique work (in my case, at least !).

In i18n.module, replace the i18n_path function by this one :

function i18n_path($path, $lang) {
  if (!$path || $path == i18n_frontpage($lang)) {
    return $lang;
  } elseif($alias = drupal_lookup_path('alias', $path)) {
    // TESTING : fix Views translation
    // Strips the existing language from alias, and adds the requested language
	  i18n_get_lang_prefix($alias, TRUE);
    return $lang.'/'.$alias;
	} else { // Alias for language path will be searched later
    return $lang.'/'.$path;  
  } 
}

This will affect every aliases which contain a language prefix.

Just add the following function to your template.php to translate table headers in general:

/**
 * Pass header cells through localization (manly for views)
 */

function mythemename_table($header, $rows, $attributes = array(), $caption = NULL) {
  
  if (count($header)){
  
    foreach($header as &$cell) {
    
      $cell['data'] = t($cell['data']);
    
    }
  
  }
  
  return theme_table($header, $rows, $attributes, $caption);
  
}

Im not sure if there is a cleaner way to call the native theme_table function.

This approach may be imperfect (please leave comments), but effective (no need to change merlinofchaos' code, only one view required for all enabled translations), and will allow Drupal 5.x users to view translated titles, headers, and body content when displaying a view of nodes. It also checks for translations of the view's node(s) in the the active language, using the site default if no translation has been made yet. Translate the strings in the usual place: admin/settings/locale/string/search.

There are 3 steps and it takes about 3 minutes.

Step 1
=====
Copy and paste this somewhere like template.php:

function translate_view($viewName) {
global $i18n_langpath; //es, fr, it, and so on 
$view=views_get_view($viewName);

//translate the title
print('<h1>' . t((views_get_title($view))) . ' </h1>' );

//run the view in the active language looking for results
$items=views_build_view('items',$view,array($i18n_langpath),false,3);

//remove i18n filters. without this, $view accumulates them
foreach ($view->filter as $key=>$value) {
	if ($view->filter[$key]['field']=='i18n.language')
	   unset($view->filter[$key]);
}

//are there results in the active language? if so, run the view in that language, otherwise the default
if (count($items['items']))
{
  //translate the column labels
  foreach ($view->field as $key=>$value)
    $view->field[$key]['label']=t($view->field[$key]['label']);

  print views_build_view('embed',$view, array($i18n_langpath),false,3);
}
else
   print views_build_view('embed',$view,array(i18n_default_language()),false,3);
}

Step 2
====
Copy and paste this into your view under arguments, arguments handling code (without the php delimiters of course):

if (!$args[0])
  $args[0]=i18n_default_language();

if ($args[0]) {
  $view->filter[] = array(
    'vid' => $view->vid,
    'tablename' => '',
    'field' => 'i18n.language',
    'value' => array(0=>$args[0]),
    'operator' => 'OR',
    'options' => '',
    'position' => 1,
    'id' => 'i18n.language',
  );
}

Step 3
====
Anywhere that you have access to write PHP (I'm using a custom block with panels2), call the function with your view name:

translate_view('type_the_name_of_your_view_here');

Troubleshooting
==========
Double-check your i18n settings
Clear the cache (i've seen odd things otherwise, including a print_r($view) with niftyCorners as an argument)

Another temporary approach I am using, maybe awful, but it works for header and footer.
I am on D5.7, so don't know if it works on 4.x
I set input to PHP and use a if statement on $_SESSION[language] variable:

if ($_SESSION[language] == 'it'){
   print $italianHeader;
}
elseif ($_SESSION[language] == 'en') {
   print $englishHeader;
}

Ciao,
GP

subscribing

Use the redirect module to redirect es/news_en to es/news_es.

Hi,

I've been messing about with this as well. I've come accross a similar solution as Enxox metioned (http://drupal.org/node/108117#comment-251689). A howto can be found here; http://www.computerminds.co.uk/multilingual-views-drupal-when-using-i18n...

But I'm using cck viewfield instead.
So you'll need cck and the extra viewfield modules.

What I've done is the following;
1 - create a new content-type, I called it page-view
2 - edit content-type -> Add field -> View field (select list)
3 - edit content-type -> Display fields -> View field -> Teaser and Full both as 'use view page settings' (this way the module uses the settings you've made in the view itself)
4 - edit content-type -> Manage fields -> View field -> configure
5 - under allowed views i checked all the views that are allowed to be inserted into the node

6 - I've created a view for each language on my site ie. news_en, news_fr, news_de etc...

Now instead of adding a view to my menu I add a page-view content-type.
I can change the title, body etc etc and insert a view news_en.
Save the node and click translation -> translate the title, body etc to French in this case and set the cck field to news_fr

You can keep doing this for each language :) Just make sure you've cloned your view to each language :)

Et voila :)

Cheers,
Bartezz

Hello thks a lot for the smart solution with viewfield module

I was already using this module in my website so I didn t need to add anything new.

I just want to add that in drupal 6 last view module , you can filter the views to show results related to the active language ( i18n argument in view )

So you don t need to create a new view for other translated version , just one view for all translated node, and maybe you ll need to use "all" as viewfield argument

I think it s a good temporary solution , untill it becomes possible to associate a translated view,

There's a module called "Views content panes" in the CTools package (http://www.drupal.org/project/ctools). This module lets you add a view to any node panel you create. And since you can translate any node to any language you want, all you have to do is to add the same view to the translated node.