Hi,
We had an issue trying to update a post with an article we wrote.
An update in text in the “SiteOrigin Editor” widget was not updating as expected. It would just seem to fail to update.
We found out it was due to an emoji – ? this one to be exact.
I believe it crashes SiteOrigin as it silently fails and reverts the text to the unedited text content. There is an option to restore (meaning it saves the content somehow) but still does not update correctly.
We had to test each paragraph to figure out where the issue was.
Could you please add some error handling, at the very least throw an exception that lets users know that they have an unsupported character in their text so that they can change their content accordingly?
Cheers,
Justin
Hi Justin,
We’ve received a report of this quite a while ago of this happening when mod_security is present and has an aggressive ruleset. I would double check with your hosting provider to confirm if this is the case and if so, if there’s anything that can be done to avoid the emoji causing the POST to get rejected.
Unfortunately, this filtering and content rejection is done completely separately to WordPress so there’s no direct way we can detect when this happens.