Hi Clinton,
I am unable to reproduce this error on WordPress 5.1.1. Can you confirm you have a good connection and there are no plugin conflicts?
Kyle
Hi Kyle,
I disabled every plugin, and enabled the twentynineteen theme. I recreated this issue on a completely different website using the latest WordPress version.
Hi Clinton,
I’m glad you were able to recreate the error on another system. Can you provide me step-by-step instructions and I will try to reproduce the error again today? I would like to open a bug report for the main trunk of WordPress.
This defect has the potential to be a heightened concern – especially if the Gutenberg editor is interpreting text as SQL or as a script – that could open up other security concerns. I’m not certain that’s what’s happening here, but I would like to understand better what’s going on and escalate to the WordPress developers.
Thanks for following up Clinton.
Kyle
Turns out it was a permission issue with my web host. I’ve asked them for further clarification on what they white listed to fix the issue. I’ll post this if/when they tell me.
Here’s a screen capture of the problem. https://imgur.com/BKntRed
Thanks Clinton. Sorry you’re dealing with this frustration, but glad it’s not a more widespread issue with WordPress.
Take care!
Kyle
The resolution was for my web host to white list a rule in their firewall, which was a false positive response to the post update activity of the Gutenburg editor. It is likely a common issue with web hosts. Maybe the way saves are initiated in the new WordPress editor can cause a firewall red flag.
Thanks for your assistance.