Closed (fixed)
Project:
Webform Localization
Version:
7.x-4.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
6 Dec 2012 at 07:58 UTC
Updated:
10 Dec 2016 at 14:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
danchadwick commentedI apologize, but I don't understand this issue and I'm not very familiar with translation. I don't see the settings that you refer to in the webform source. Are you using another modules for webform translation?
Comment #2
danchadwick commentedComment #3
dame commentedTranslation settings are provided by the "webforms Localization" module, I am having the same issue!
https://www.drupal.org/project/webform_localization
Comment #4
danchadwick commentedI'm moving this issue to the webform localization issue queue for assistance. If there is actually an issue in webform, I would be most grateful for some background and assistance with a patch.
@dame -- Can you provide some detailed instructions to reproduce the issue. I am not following exactly what suppyx is saying. It seems that the conditionals work properly in the original webform, but not in the translated webform? And I can't tell if all conditional fields are hidden, all are shown, or which fields are having an issue.
I'm happy to coordinate a fix for this issue, but I'll need some help. Many thanks.
Comment #5
gge commentedHello,
I explained this issue here.
Thank you!
Comment #6
Frederic wbase commentedHello
Based on the comments of gge in #5 i've created a patch that alters the js so it uses the correct webform id.
Also changin this status to "needs review".
grts
Frederic
Comment #7
Frederic wbase commentedComment #9
Frederic wbase commentedFixed a small issue, it was not working on the source node anymore
Comment #10
gge commentedHello,
Just tried your patch and it does not working on the source node. Also I want to mention that I'm using Entity Translation.
Also there is a notice:
Comment #11
Frederic wbase commentedHello gge
i've hardcoded array key 11, should be better dynamic.
feel free to adjust the patch.
Further more there should be an extra check if tnid != nid but that one is already included in #9
grts
Frederic
Comment #12
Stevel commentedI've updated the patch to include only the necessary changes, and made it work for any array key.
Comment #13
Stevel commentedAccidentally left in a debug statement. Updated patch
Comment #16
Stevel commentedThe testbot fails also fail in HEAD, so these have nothing to do with this patch.
Comment #20
Stevel commentedThe patch doesn't apply anymore. Rerolled the patch without changes
Comment #21
joseph.olstadHi Stevel, thanks, I reviewed the patch.
It looks like it should work in the case that the option "Keep a single webform across a translation set." is selected
however if that option "Keep a single webform across a translation set." is not selected we'd need an additional check to make sure that the current behaviour stays.
once this change is added we should be a bit closer to getting this in
also, a minor formatting tidbit, string concatenation according to coding readability standards requires a space before and after the "."
Comment #22
Stevel commentedUpdated the patch according to #21.
Comment #24
Stevel commentedFollowing the 7.x-4.x-branch changes...
Comment #26
joseph.olstadThanks Stevel!
Comment #28
knalstaaf commentedAre you guys sure this is fixed please?
I'm having the very issue again in 7.x-4.10 (and -dev 02/11/2016).
Edit: the issue occurs when the webform is used as a block: #2829894: Conditionals not working in Webform block
Comment #29
joseph.olstadReview possibility of regression being reported as described in previous comment.
Comment #30
joseph.olstadsee related issue for conditionals when used as a block
#2829894: Conditionals not working in Webform block