Add multi language support

If you store it with variable_get() and variable_set(), with a variable for each page, instead of in the contact table, we can add those variables as multilingual variables in the settings file, and a separate variable will be stored in the variables table for each language. See this : http://drupal.org/node/313272

You wouldn't need an .install file with the module anymore.

db_query() in contact_redirect_contact_admin_edit_submit() and contact_redirect_get() would need to be modified to do variable_get().

At this point I would not know how to preform translation on the redirection. I used a trick - the destination pages have the same path but because the language prefix gets added before the path alias, a different page can be reached for each language.

I don't think it will work as suggested. I replied in the thread here :

http://drupal.org/node/306662#comment-1389966

I don't have any experience with triggers and actions yet, so I can't make suggestions on that matter.

If you don't want to use the variables table but would like to provide multilingual support, my other suggestion is that your module could have it's own table instead of adding a field to the contact table, with cid, language, and redirect fields.

It seems more complicated than using the variables table because i18n module takes care of translating variables.

Your module could query this table with a method similar to this :

function contact_redirect_get($cid = FALSE) {
  global $language;
  if ($cid) {
    $redirect = db_result(db_query("SELECT redirect FROM {TABLE_NAME} WHERE cid = %d AND language = %s", $cid, $language->language));           
  }
  else {
    $redirect = '';
  }
  return $redirect;
}

It would require lots of changes elsewhere too, maybe with redirect fields for each language, one for each item returned by language_list().

Sure - if you build your module to use it's own table, and said table includes a field for language, I can help with the language detection process.

I recommend making these changes available only with the 6.x version, because language support is somewhat different in core with 5.x. I've used the 6.x patch in the other issue and it works well.

I don't think another module is needed if we find a way that is simple to implement and maintain using the core API.

What about calling translation_path_get_translations() on the path you retrieve from your query, then selecting the appropriate path from the array according to the user selected language, as defined by $language?

That way your module does not need to store the other language path, just the default language. Core provides the translation path.

That would be great - store one path, and when your module retrieves it, use translation_path_get_translations() to get the paths for all translations to that content, then determine which one to use by looking at the current user's language in the $language variable.

I don't know if there is such a module - but here's what I think you could do without too much more code. No other module required but core modules.

/**
 * get the contact redirect for a particular contact category
 */

function contact_redirect_get($cid = FALSE) {
  if ($cid) {
    $redirect = db_result(db_query("SELECT redirect FROM {contact} WHERE cid = %d", $cid));
    // new code using the function and variable mentioned above
    if (module_exists('translation')) {
      // get the system path
      $source = drupal_lookup_path('source', $redirect);
      // get all translation paths for that system path
      $paths = translation_path_get_translations($source);
      // choose which path to use according to user language
      $systemPath = $paths[$language->language];
      // now get the path alias for that system path
      $redirect = drupal_get_path_alias($systemPath);     
    }   
  }
  else {
    $redirect = '';
  }
  return $redirect;
}

---------------------------------------------------------------------------------------

This is how I tested the functions in a template file to figure out exactly what is needed for this module

// check out how drupal_lookup_path() works;
echo $_GET['q'] . '<br/>';
$alias = drupal_lookup_path('alias', $_GET['q']);
echo $alias . '<br/>';;
$source = drupal_lookup_path('source', $alias);
echo $source . '<br/>';

// check out how translation_path_get_translations() works;
$paths = translation_path_get_translations($_GET['q']);
echo '<pre>';
print_r($paths);
print_r($language);
echo '</pre>';
echo $paths[$language->language] . '<br/>';
echo drupal_get_path_alias($paths[$language->language]);

The output will be something like this :

node/1620
zoom-coming-your-neighbourhood
node/1620

Array
(
    [en] => node/1620
    [fr] => node/1621
)
stdClass Object
(
    [language] => en
    [name] => English
    [native] => English
    [direction] => 0
    [enabled] => 1
    [plurals] => 0
    [formula] => 
    [domain] => 
    [prefix] => en
    [weight] => 0
    [javascript] => 
    [dir] => ltr
)

node/1620
zoom-coming-your-neighbourhood