CiviCRM Community Forums (archive)

When creating Drupal webforms for sites in multiple languages (english/french), I usually created two separate nodes with the same configuration and linked then as translations. In the end, they created the same type of activities in CiviCRM, so this duplicaiton of forms wasn't a big deal.

However, I have a project where we have complex forms, with multiple tabs, lots of fields, conditionals, etc. Cloning/translating the node wasn't very practical. If we forgot the smallest changes, the nodes would be out of sync.

So I turned to the "webform_localization" module (https://www.drupal.org/project/webform_localization). It's clever, very practical, but has a few patches in the issue queue that need to be applied for it to work properly (for example: if you want field conditionals to work).

One thing that didn't work, and took me a bit of a while to figure out, is that webform_civicrm processing does not work on the node in the "other" language. We are using "localization by string translation", with both options enabled. This was probably not the best idea, and next time I might go with "localization by sync".

Anyway, for "localization by string translation", I had to patch webform_localization.module so that civicrm processing works:

<pre>
--- a/webform_localization.module
+++ b/webform_localization.module
@@ -227,6 +227,7 @@ function webform_localization_node_view($node, $view_mode) {
     $source_node = node_load($result);
     // We replace the webform with the node translation source.
     $node->webform = $source_node->webform;
+    $node->webform_civicrm = $source_node->webform_civicrm;
 
     // This fool webform_node_view to avoid errors with drafts in between pages.
     $translation_nid = $node->nid;
</pre>

Any other experiences with webform/civicrm/multi-lingual? Any suggestions?