Hi,

I was wondering if you could tell me what this module does differently from https://www.drupal.org/project/webform_localization? It would be good to state this on your project page - or potentially merge the two projects since this module only has a few sites using it.

Cheers.

Comments

joel_osc created an issue. See original summary.

Johnny vd Laar’s picture

Status: Active » Closed (won't fix)

The difference is the method of translating. For webform localization you can translate the webform by using the Drupal Locale system. For this a user needs to have permissions to translate the website. In my opinion webforms are content and you shouldn't translate content with the locale system. Therefore this module makes a custom translation system. I also think that the interface of this module is slightly more user friendly.

eddie_c’s picture

Could you explain in a bit more detail the difference between a translation based on the locale system and how this "custom" translation system works? Can it, for example, use a different set of languages from those defined by locale at admin/config/regional/language ?

Johnny vd Laar’s picture

The problem has to do with permissions. For a locale translation you have to give the user access to all locale translations. With this module the user suffices with the permission to modify webforms. Thats the biggest difference.

joseph.olstad’s picture

Hi Johnny, thanks for this module, I've updated the webform_localization page with a link to your module, this should increase adoption of your module.
Nice work!
We did just release webform_localization 4.11 , various bug fixes. There are use cases for both of these modules. If you're using entity_translation you'll really want to check out the webform_translation module. Whatever gets the job done, good to have options, if you prefer one, use it, prefer the other, great!