API Error for specific UTF-8 chars in subject #1445
Replies: 15 comments
-
|
Are you able to find the error in the logs? We'll need to know where it went wrong. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
How old is your Postal installation? In theory this was resolved with 752558f |
Beta Was this translation helpful? Give feedback.
-
|
Running on the latest master. Also migrated everything as described here: #1164 UTF-8 is generally working, only very specific characters as this one is not working |
Beta Was this translation helpful? Give feedback.
-
|
looking at your link at 752558f exactly matches to the issue i have. The reason prob is that the subject column is not migrated to utf8mb4, thats why it works in body and not in the subject line. Also a user already complained here 752558f#commitcomment-45466226 that hes not able to use utf-8 emojis? |
Beta Was this translation helpful? Give feedback.
-
|
Interesting, emoji works for me and HeidiSQL thinks I've got the encoding everywhere |
Beta Was this translation helpful? Give feedback.
-
any idea hows that possible? |
Beta Was this translation helpful? Give feedback.
-
|
if you create a new server in Postal, does that get utf8mb4? |
Beta Was this translation helpful? Give feedback.
-
|
yeah thats weird! If i create a new 2nd server.. both switching to utf8mb4_unicode_ci. |
Beta Was this translation helpful? Give feedback.
-
|
creating a second server shouldn't affect the first one which implies your database client might be going wrong somehow when telling you the collations? |
Beta Was this translation helpful? Give feedback.
-
|
before: after: Verified it again and youre right, my mistake sorry.. Anyways the initial table stays at utf8_general_ci , and idea why migrations (as you can see above) are marked as done but the table is still at utf8_general_ci ? Having 4 different instances of postal with exactly this problem. Current workarround: The only question im having is.. how is it possible that those migrations got on all my 4 instances marked as successfully runned, even if it seems they failed / were never running? |
Beta Was this translation helpful? Give feedback.
-
|
No worries, happens to us all. I'll give a fresh install a go when I can to see what happens, it is odd that all your instances have the same error. |
Beta Was this translation helpful? Give feedback.
-
|
Actually I had a recent copy which seems to be fine, how long ago did you make the Postal instances? |
Beta Was this translation helpful? Give feedback.
-
|
maybe a year or two ago? |
Beta Was this translation helpful? Give feedback.
-
|
So it might be that the upgrade process missed yours out somehow. If you're comfortable in a database editor, you could make the fixes yourself, I'm not familiar enough with ruby to know the correct way of resolving it. |
Beta Was this translation helpful? Give feedback.






Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
Postal runs into trouble having a specific UTF-8 spacing character in the subject line.
Sending an E-Mail with a Subject Line including this spacing char:
https://www.fileformat.info/info/unicode/char/e0100/index.htm
fails with
{"{\"status\":\"internal-server-error\"}":500}Any idea how to solve it?
The character seems to be accepted when placed in the E-Mail body.
Beta Was this translation helpful? Give feedback.
All reactions