-
-
Notifications
You must be signed in to change notification settings - Fork 53
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
Fix bug where emojis in contrib title cause SQL error #390
base: 3.3.x
Are you sure you want to change the base?
Conversation
…sing in both the contrib page title and the manage contrib form field
Trials in the test environment were successful. For both the Name and the Description field, it accepted the NEW emoji without an SQL error message. |
As a note in reference to your first post. The general error I received was when I was using Safari on macOS (latest). So it's not isolated to Windows specifically in case that's helpful to this issue. |
That's very interesting - I tried this quite a few times with @Crizz0 and it was erroring for him (Android) and working for me (Mac). @danieltj27 Could you please share the precise steps you used when you saw this error on Mac? I would like to try and replicate it on my Mac... then I won't have to keep lugging out my heavy Windows laptop 😆 |
I submitted a new revision of an extension on phpBB.com. In the Submitted the revision returned the error I reported. |
Thanks @danieltj27, I can replicate this on my Mac now with those instructions. This is becoming quite a frustrating bug isn't it!
Could it be that the charset of the Titania tables is different than the rest of phpBB? |
Interesting bug that a few people have noticed @LukeWCS @Crizz0 @vinny @danieltj27 - in Titania, if you're on Windows or Android, and use an emoji like 🆕 in the new contrib name it would spit out an SQL error like
Incorrect string value: '\xF0\x9F\x86\x95\x0AS...'
when trying to submit. It's hard to reproduce because it seems to be fine on Mac.My findings were that due to some code deep in Titania, unlike the other fields the actual contrib message/description seemed to be immune from this because it was being parsed to XML with the s9e text formatting library.
I've followed that lead to import s9e and parse/unparse the contrib names.