Multiple Plugin Errors Appearing in WordPress Editor (wpcom-live-preview etc!)
-
Hello WordPress Support Team,
We’re currently experiencing an issue in the WordPress editor on our site celoxis.wordpress.com.
When editing posts, several WordPress.com editor plugins are showing errors such as:
- wpcom-live-preview
- onboarding-next-step-after-publishing-post
- start-writing-flow
- track-inserter-menu-events
- wpcom-site-editor-load
The editor opens, but these plugin errors appear at the top of the page, and we’re concerned they may affect editing, previews, or publishing functionality.
Could someone please check if this is related to our site specifically or if it’s a broader WordPress.com issue?
adding @modlook
Thank you for your assistance.
Best regards,
Team CeloxisThe blog I need help with is: (visible only to logged in users)
-
I think this is a broader problem with WordPress as a whole. I’m getting the exact same errors across all of my sites on desktop.
-
Thanks for confirming. We’re seeing the same issue on our site as well. We’ll wait for an update from the WordPress team.
-
I am facing the exact same problem on WordPress.com Free plan. Multiple Jetpack errors appear when creating a new post. Glad to know it’s not only my site.
-
-
-
Hi everyone!
These errors were caused by a bug in a platform update (Gutenberg 23.3.1) that was deployed earlier today. It affected the block editor across WordPress.com sites on all plans, causing internal components like wpcom-live-preview, start-writing-flow, and others to display error messages.
Our engineering team identified the issue right away and rolled back the update. The editor should now be working normally again.
To clarify: this was not related to any specific plan. It affected Free, Personal, Premium, and Business sites alike. If the editor started working after a plan upgrade, the timing was coincidental — the fix was the rollback happening in the background.
Please do a hard refresh of your browser (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) to make sure you’re loading the corrected version. Your content was never at risk.
If anyone is still seeing errors after refreshing, please let us know.

