Bug: Error Message When Using Symbols In The Open Graph Description
BOFHJunior
This post is for Helix Ultimate Version: 2.1.2, SPPB Version: 5.5.4, Joomla Version: 5.2.5, no Template is used.
When i use the 💡, 🤔, 🌹, 💐, 💍 or 📷 Symbols in the SPPB Options -> SEO -> Open Graph Description field (https://i.imgur.com/oyShlCu.png) i cannot save these changes because of an error message:
For 💡 it is: Error Incorrect string value: \xF0\x9F\x92\xA1 for column Database Name.g39cq_sppagebuilder.og_description at row 1
For 🤔 it is: Error Incorrect string value: \xF0\x9F\xA4\x94 for column Database Name.g39cq_sppagebuilder.og_description at row 1
For 🌹 it is: Error Incorrect string value: \xF0\x9F\x8C\xB9 for column Database Name.g39cq_sppagebuilder.og_description at row 1
For 💐 it is: Error Incorrect string value: \xF0\x9F\x92\x90 for column Database Name.g39cq_sppagebuilder.og_description at row 1
For 💍 it is: Error Incorrect string value: \xF0\x9F\x92\x8D for column Database Name.g39cq_sppagebuilder.og_description at row 1
For 📷 it is: Error Incorrect string value: \xF0\x9F\x93\xB7 for column Database Name.g39cq_sppagebuilder.og_description at row 1
As you can see in the Screenshot these Symbols in the Meta Description field are no problem and can be saved. Only when used in the Open Graph Description field these error messages appear.
Other Symbols like ✓, ☎, ✅, ✊, ✉, 📷 or ❗from the same font Segoe UI Emoji are no problem and can be saved in the Open Graph Description field without an error message.
Expecation: All Symbols from the font Segoe UI Emoji can be used in the Open Graph Description field.
Ofi Khan
Accepted AnswerHello BOFHJunior,
Thank you for reaching out to our technical support forum. I’m sorry to hear about the trouble you’re experiencing.
I will talk to the developer about the issue and will update you.
Best regards
Ofi Khan
Accepted AnswerSorry, this is not fixed yet. We have not got many requests for this. However, we will check the issue. It might be delayed.
Ofi Khan
Accepted AnswerJust checking in to see if you have feedback on the provided solution. If the answer resolved your query, you can mark it as accepted to close the post and guide others with similar questions. You’ll find a button to accept answers below each comment.
If you need further assistance, feel free to let us know!
Ofi Khan
Accepted AnswerApology for the inconvenience. I had reported the issue to the developer team when I got it. Unfortunately, the issue still remains. I have asked the team to give the issue priority and fix it on the next release. The rest is up to the developer team decision.
You can keep the ticket open or closed.