This is an FYI – We have a multi-site sandbox server set up to mimic our multi-site live server. With the latest update 5.3 and Gutenberge enabled (Classic Editor OFF) we encounter an error:
The editor has encountered an unexpected error. [Attempt Recovery][Copy Post Text][Copy Error]
On the sandbox server, we used the following process to debug:
– Clear browser, server caches and browser history
– Open an existing Gutenberg page
– Scroll to an existing text block
– Click (+) to add a new block
– Scroll to Layout Elements
– Click Layout Elements
– if an error is produced, disable a plugin and repeat. If an error is not produced, the last plugin disabled is a likely candidate for incompatibility.
– repeat for all installed plugins
** an error box is generated **
The editor has encountered an unexpected error. [Attempt Recovery][Copy Post Text][Copy Error]
Here is the resulting output of the Copy Error button:
Pc@https://ales-wp-dev.ales.ualberta.ca/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0:66:441
Dg/<@https://ales-wp-dev.ales.ualberta.ca/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0:76:255
T@https://ales-wp-dev.ales.ualberta.ca/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0:87:146
ph@https://ales-wp-dev.ales.ualberta.ca/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0:216:50
lh@https://ales-wp-dev.ales.ualberta.ca/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0:126:411
O@https://ales-wp-dev.ales.ualberta.ca/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0:121:71
ze@https://ales-wp-dev.ales.ualberta.ca/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0:118:14
mg/<@https://ales-wp-dev.ales.ualberta.ca/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0:53:49
unstable_runWithPriority@https://ales-wp-dev.ales.ualberta.ca/wp-includes/js/dist/vendor/react.min.js?ver=16.9.0:26:340
Ma@https://ales-wp-dev.ales.ualberta.ca/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0:52:280
mg@https://ales-wp-dev.ales.ualberta.ca/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0:52:498
V@https://ales-wp-dev.ales.ualberta.ca/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0:52:431
Be@https://ales-wp-dev.ales.ualberta.ca/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0:119:77
xi@https://ales-wp-dev.ales.ualberta.ca/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0:39:175
After systematically enabling and disabling our plugins (leaving Page Builder by SiteOrigin enabled) we found the error vanished when we disabled:
WP Log Viewer – Version: 1.2.1 – Last Updated: 2 years ago – Requires WordPress Version: 3.9 or higher – Compatible up to: 4.8.11
Hi Bgrier
Sorry to hear about this hassle.
I’ve logged the conflict on GitHub. Thanks for taking the time to troubleshoot and inform us of the issue. Hopefully, you can find a suitable replacement for WP Log Viewer.
Query Monitor is one possible alternative although it’s a much more complex plugin than WP Log Viewer.
Hi Andrew, no worries — we needed to solve it and the plugin-debug process was worth our internal time as our process needed a bit of a tune up.
We’re now using WP Security Audit Log which meets our needs.
Thanks for the quick followup — have a good one!
–Brad
Super, thanks for the follow-up and plugin recommendation. I’m glad to hear you found an alternative.
Cheers for now :)