New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SELF HOSTED | Error | 500 error after adding emoji to subject line #1029
Comments
I have tested by copy and pasting the email subject and body to a new email and everything works as predicted. I am able to edit the original email by clicking the drop down next to the email and selecting the "Edit" option. However, clicking the email itself produces the 500 error. To be more succinct: Attempting to navigate to this URL fails with the 500 error: But this URL works as expected: |
I have a couple of questions:
|
Hello,
|
It's possible we haven't accounted for that emoji although all standard ones should be. Well look into that. Please get us the contents of those non-Mautic files so we can examine them on whether it's a security threat we need to deal with. I'm slightly concerned that Symfony is loading app/bundles/CoreBundle/Controller/Cller.php and CommonChp if they are not Mautic. But they look really odd so I'm wondering if it's just a logging and or copy paste issue as well. If you don't find them, then Id say it was just that. |
Hello Alan, I'm browsing my VPS at the moment and don't actually see those files as existing. [root@thistlebean01 Controller]# pwd Any suggestions? |
I think it was just a copy/paste issue then and nothing to worry about. But for the emoji issue, to restore access, edit the audit_log table and find where object = email and set the details to Exactly which emoji is 󾍠 on that page? |
Great. The emoji is the animated ?? (not sure if it will show up here) With regards to the audit_log fix, please could you let me know which field(s) I need to change/update? It appears there are quite a few duplicates for email ID 1? |
Try running this query to see if it reveals any broken serialized strings.
(if you used a table prefix, prepend it to audit_log) If it finds bad entries, just replace the details contents with |
Great. Thanks. Here is the SQL query I used in the end: UPDATE audit_log SET details = REPLACE(details, '^a._[^}]$', 'a:0:{}') WHERE details REGEXP '^a._[^}]$'; However, the 500 error when viewing that particular email still shows up. Anything else I can investigate? |
Hello,
I receive a 500 error after saving an email with an emoji in the subject line.
Here are the error logs:
I saw another post with a similar issue but in relation to leads.
Is the fix for this the same process? If so, please help me out?
I'm running the latest version.
Thanks!
The text was updated successfully, but these errors were encountered: