[MGNLMAIL-190] Cannot use special characters in mail subject in 5.6.1 Created: 19/Sep/23 Updated: 14/Dec/23 Resolved: 29/Nov/23 |
|
| Status: | Closed |
| Project: | Magnolia Mail Module |
| Component/s: | None |
| Affects Version/s: | 5.6.1 |
| Fix Version/s: | 6.0.0, 5.6.2 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Richard Gange | Assignee: | Canh Nguyen |
| Resolution: | Fixed | Votes: | 5 |
| Labels: | None | ||
| Σ Remaining Estimate: | 0d | Remaining Estimate: | 0d |
| Σ Time Spent: | 3d 1.5h | Time Spent: | 3d 1.5h |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Attachments: |
|
|||||||||||||||||||||||||
| Issue Links: |
|
|||||||||||||||||||||||||
| Sub-Tasks: |
|
|||||||||||||||||||||||||
| Template: |
|
|||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
|||||||||||||||||||||||||
| Task DoD: |
[X]*
Doc/release notes changes? Comment present?
[X]*
Downstream builds green?
[X]*
Solution information and context easily available?
[X]*
Tests
[X]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
|||||||||||||||||||||||||
| Bug DoR: |
[X]*
Steps to reproduce, expected, and actual results filled
[X]*
Affected version filled
|
|||||||||||||||||||||||||
| Release notes required: |
Yes
|
|||||||||||||||||||||||||
| Date of First Response: | ||||||||||||||||||||||||||
| Epic Link: | Support | |||||||||||||||||||||||||
| Sprint: | DevX 51 | |||||||||||||||||||||||||
| Story Points: | 2 | |||||||||||||||||||||||||
| Team: | ||||||||||||||||||||||||||
| Work Started: | ||||||||||||||||||||||||||
| Approved: |
Yes
|
|||||||||||||||||||||||||
| Description |
|
Trying to use any special characters in the subject of an email sent by Magnolia doesn't work. The characters are converted to unicode. Reproduce
Expected Actual Notes
|
| Comments |
| Comment by Marvin Kerkhoff [ 10/Nov/23 ] |
|
We also found this issue in 3 different Customer Projects since Version 5.6.1 version of this module. It was fine at 5.6 We see this also for all Umlaut which are special characters as well. I am happy to see progress here. ;D |
| Comment by Manuel Haug [ 14/Nov/23 ] |
|
We also found this issue in a customer project. Is there any ETA on when this is going to be solved? |