Closed (won't fix)
Project:
Webform
Version:
6.x-3.x-dev
Component:
Code
Priority:
Minor
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
7 Apr 2009 at 09:13 UTC
Updated:
23 Aug 2014 at 12:57 UTC
Jump to comment: Most recent
Comments
Comment #1
matteoraggi commentedYou are right, but yo uare speaking of a problem that statistically happen probably a lot less of 1% of times that webform is being used, so this feature risk to became one of the lowest in tasks priorities.
Comment #2
dspachos commentedI have the same problem.
Is there any solution?
thnx
Comment #3
adampdp commentedI do not use webform, but I have the same problem. Notifications arrive not in the language selected by the user, but in the site language selected by the submitter. I think it is an issue with notifications. For example if user A is viewing the site in language X and adds a comment, the notification of the comment arrives to user B in language X, no matter what the preferred language of user B is. Any solutions would be great!
Comment #4
quicksketchI do not think this is particularly a bug report, because the language used depends on who the e-mail is being sent to. Yes if the e-mail is being sent to the owner of the node, it should probably be in the node language. However if it's being sent to the user that filled out the form, then whatever language they prefer should be used. In a 3rd scenario, perhaps the e-mail is being sent to a site administrator, in which case the language might not be that of the node or the user.
The only feasible way I can think to solve this is to make an option when configuring e-mails. Fortunately in 3.x each e-mail is configured separately, meaning you could send one e-mail in the user's language and one e-mail in the administrator's language. Honestly though this seems like over-complication of things, but translation is never easy I suppose. This is a low priority feature for me, especially considering Webform doesn't work that well in multiple languages to begin with.
Comment #5
quicksketchMoving back into the 3.x queue.
Comment #6
danchadwick commentedThere won't be further feature development in the X.x-3.x branches. Closing for lack of activity.