Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I have a website with the i18n package so that I can support several languages, Spanish and English right now. I have created a webform survey in Spanish and now I am about to translate it into English. I am offered the webform header for translation, but the components have disappeared. I expected to see a clone of the original webform so that I only had to translate strings, not to build all the components again. Is it a webform issue or an i18n issue? I don't think this is the expected behaviour.
Comments
Comment #1
chrisada commentedI can confirm this problem.
Comment #2
quicksketchThis is because currently i18n and localizer modules use revisions for different translations of nodes. Because webform doesn't have revision support, the components are likely lost when creating the new revision.
Comment #3
giorgoskAs it was pointed out in another issue for webform
http://drupal.org/node/258894
Node clone does a good job copying over the actual webform components
couldn't node_clone be integrated with webform ?
And perhaps use the node_clone functionality if that module is enabled ?
Comment #4
quicksketchNode clone will remain a separate module. It does the job perfectly as a generic solution there's no need to maintain the same code in two places.
Comment #5
Farreres commentedHey, no need to duplicate code, just add a dependency and call this module functions. That's all, simple and elegant solution.
Comment #6
quicksketchHmm, I don't understand why to make it a dependency. It works perfectly well as a simple add-on module. Install node-clone, click the clone tab. No more customization is necessary, we wouldn't get anything by having Webform call the functions instead of node clone.
Comment #7
Farreres commentedAs I see it, node clone will create two nodes, with different IDs. But the problem we were stating here is that I want ONE node with multiple language translations. That is, one node that is rendered differently depending on the language. Someone suggested translations in both i18n and localizer are supported via revisions. And this more or less complies with the need of having one node translated to two languages instead of having two copies of one node, each copy translated into one language. I know it's a complex matter but I don't want to copies of each node.
Comment #8
quicksketchOh I see. Yes, the proper way to handle this is to make Webform revision-aware (for Drupal 5) and language-aware (in Drupal 6), however, node clone module won't play into that scenario at all. So the request remains the same, as I mentioned in #2, we need to make Webform aware of these facilities.
Comment #9
quicksketchThis issue seems to have more activity in it. Let's consolidate there: #245424: Make Webform multilingual (i18n) aware through contributed modules.
Comment #10
zilverdistel commentedAllow me to reopen this as a feature request, because the issue title describes exactly my problem. When I translate a webform node in drupal 6, all components are copied into the translated node. With drupal 7 however, this doesn't seem to be the case.
I allready subscribed to #245424, but I believe this issue (#115292) is not about translating the labels.
Comment #11
quicksketchI probably won't be looking into this issue as I don't currently have any multilingual sites. Happy to look at patches though.
Comment #12
joostvdl commentedSubscribe
Comment #13
daften commentedsubscribe
Comment #14
quicksketchThese days I think https://drupal.org/project/webform_localization would be responsible for this problem. Webform has provided tools for translation, but another module needs to provide the UI for this difficult problem.