Webform in Multilingual CiviCRM, Best Practice?

[Luciano S.]

Hi,

I have a Multilingual CiviCRM 4.4.4 (en / fr) where I expose a Webform_CiviCRM for Event Registration.
The Drupal (7.26) is multilingual as well.

What is the best practice to make the Webform multilingual?
If I use one Webform per language (different nodes) is there any syncronization between CiviCRM language labels (custom field, option values, etc) and the Webform? What I mean is if I have a Webform 1 in english that gets all the CiviCRM english labels (by default), is there any way to create a Webform 2 in french that gets (live) all the CiviCRM french labels?

cheers!

[Coleman Watts]

I really don't know, I've never tried it. Webform does support multilingual options on the same form AFAIK but I haven't done any work yet to integrate it with live options from civicrm. It would be interesting to investigate what will be needed to make that integration.

[Luciano S.]

If I'm not wrong, you get the option values using civicrm API, don't you?
So first of all we need to take a look if civicrm API is ready to retrieve  "localized" values passing the language as parameter.

Since I have a a very close deadline I think I will try the approach of having static options and try this module Webform translation (https://drupal.org/project/webform_localization)

Let you know the updates

cheers

[Coleman Watts]

In version 4 we do get options via the api. So if CiviCRM "knows" what language you are working in (e.g you have enabled the option to follow cms language) and you enable "live options" on the webform, then it might "just work" out of the box. Have you tried it?
Err, that might not work perfectly with events. Might want to try a simple field like gender first and see how that goes.
Please do try and report back it would be very helpful.

[Luciano S.]

Hi Coleman,

I did try to enable in CiviCRM Localization -> Inherit CMS Language
This gets the option values according to the language selected in Drupal out of the box (nice!)

But for the Fields' labels, since they are stored in the Drupal Layer when you create the webform, I have to Translate them, which is not a problem with Webform Localization module

cheers!

[Coleman Watts]

Cool. Glad the options work. Seems like it would be useful to integrate Webform-CiviCRM with Webform-Localization so the multiple labels were automatically populated. If you or any of the (probably small) number of organizations using multilingual Webform+CiviCRM wish to sponsor such an improvement, let me know.

[Luciano S.]

Tx Coleman, this is a specific project with multilingual needs, but it's not the general case for us

I think we will be more interested in sponsor some integration between Webform-CiviCRM and Features / Node Export modules. Or if there is another way to easily export the Webform CiviCRM between installations.
As far as I tested Features / UUID / Node Export modules works well for Webform migration, but the CivCRM layer of the Webform-CiviCRM is not exported.
Do you have in mind or any plan to get into this issue?

cheers!