Closed (outdated)
Project:
Contact Emails
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Jul 2017 at 10:58 UTC
Updated:
8 Mar 2024 at 08:38 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
scott_euser commentedAre you looking at the stable release? Multi-lingual is available in the development branch which should be released as stable shortly. You're welcome to test the development branch which does have an upgrade path (note that by updating, you won't be able to roll back to the current stable release - you'll need to wait for the new stable release to come up to move to that - I would recommend backing up first before updating to a development branch).
If this issue is related to the development branch, please reopen.
Comment #3
adhariwal commentedI now tested it with dev branch and added two email templates one for English and other for Hindi, while sending a test email my site language was Hindi and I received two emails one in Hindi and other English.
Comment #4
adhariwal commentedComment #5
adhariwal commentedComment #6
scott_euser commentedCan you confirm whether you created 2 emails or whether you created 1 email then translated that single email?
Comment #7
adhariwal commentedI created two emails one for each language.
Comment #8
scott_euser commentedHmmm I think we need to consider this a bit.
Perhaps we need to give control to the site builder control per email to decide its behaviour.
Thoughts?
Comment #9
scott_euser commentedIf you do actually translate the email rather than create 2 emails, only the email in your current language gets sent.
Comment #10
adhariwal commented@scott_euser I agrees with the use case you have narrated. Also I don't think adding content translation is a good idea here. Can't system choose the appropriate email template based on the current language of the site?
Comment #11
scott_euser commentedCould you explain why you think content translation is not a good idea? I would prefer to use the tools we have available to us rather than create our own - keeps it easier to support. Happy to hear arguments against that.
Comment #12
astonvictor commentedI'm closing it because the issue was created a long time ago without any further steps.
if you still need it then raise a new one.
thanks