-
AuthorPosts
-
December 9, 2018 at 3:35 pm #1042746
Hello, after installing WP 5.0 and Enfold 4.5.1 successfully, I can not edit a past post or create a new post. I get this message:
“The editor has encountered an unexpected error”
Here’s what it looks like: https://www.screencast.com/t/JXH9BsCpDV
“attempt recovery” does nothing. “copy error” adds this to my clipboard:
TypeError: Cannot read property ‘decodeEntities’ of undefined
at https://mikereinold.com/wp-includes/js/dist/editor.min.js?ver=9.0.4:55:121589
at ph (https://mikereinold.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:97:88)
at eg (https://mikereinold.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:125:307)
at fg (https://mikereinold.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:126:168)
at wc (https://mikereinold.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:138:237)
at gg (https://mikereinold.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:135:160)
at Ca (https://mikereinold.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:133:365)
at og (https://mikereinold.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:150:95)
at Rd (https://mikereinold.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:150:173)
at bb.render (https://mikereinold.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:200:185)Any ideas? I’m not that smart :)
Thanks so much in advance for any help!
December 9, 2018 at 8:01 pm #1042799Hey mmr1234,
Thanks for the login, I see you have many “mixed content” errors, where your site is https but it’s trying to load scripts from http
Really Simple SSL should solve this.
You also have JS errors:inspector.js - Uncaught TypeError: Cannot read property 'InspectorControls' react-dom.min.js - TypeError: Cannot read property 'decodeEntities'
I believe these are scripts from some of your plugins, Try disabling your plugins. If that resolves the issue, reactivate each one individually until you find the cause.
Best regards,
MikeDecember 10, 2018 at 1:33 am #1042861I disable all plugins and still have the issue.
December 10, 2018 at 2:39 pm #1043098Hi,
The js error is coming from/wp-includes/js/dist/vendor/react-dom.min.js
which is not a standard WordPress directory or file, I tried to disable your plugins but I got a WP Engine warning.
I see you have some “must use” plugins from WP Engine, I wonder if the js is apart of one of those plugins?
Please ask WP Engine if this js is from them and to try disabling it.
If you need your site back ASAP, I believe that WP Engine offers free staging sites, which are copies of your site on temp servers to test with, you could roll your site back to WP 4.9 then create a staging site that is updated to WP 5 that we can continue to work on resolving this issue without it affecting your live site.
*just a thoughtBest regards,
MikeDecember 10, 2018 at 3:02 pm #1043103Thanks Mike, that’s not a WP Engine error, that is just a warning to say back up your site when disabling plugins, you can just click that away as the site backs up everday on it’s own. I again tried to disable all plugins and it didnt help.
I have other sites running Enfold on WP 5.0 on WP Engine and not having an issue so, i don’t think it’s any of there “must use” plugins.
I will work on figuring out that js error, but if anyone has any other thoughts I would appreciate it!
December 10, 2018 at 9:32 pm #1043361Hi mmr1234,
That comes from Gutenberg, it uses React under the hood. Are you using Gutenberg?
Best regards,
VictoriaDecember 11, 2018 at 12:50 am #1043451I have WordPress 5.0 Installed, yes.
December 11, 2018 at 3:39 am #1043530Hi,
Thank you Victoria, this file is in WP 5.
So now it a matter of finding the conflict, it seems that our login is no longer valid.Best regards,
MikeDecember 11, 2018 at 1:09 pm #1043735Sorry I was playing around with back ups and restore points. It should be back again Mike, I would appreciate any more guidance you may be able to offer.
I have installed the “classic editor” plugin to disable the Gutenberg editor and I can now access my posts. Not sure if that helps you diagnose in anyway.
THANKS!
December 12, 2018 at 5:13 am #1044108Hi,
That is very interesting,
When I open one of your pages, I see this error:Failed to load plugin url: https://your-site.com/wp-content/plugins/easy-social-share-buttons3/lib/modules/click-to-tweet/assets/tinymce/js/tinymce-essb-ctt.js
I know that you tried deactivating your plugins without correcting the issue, but in order to test and find out what is going on we will want to make some temporary changes to your site like deactivating your plugins.
Would it be possible to create a staging site so anything we do won’t effect your live site?Best regards,
MikeDecember 13, 2018 at 12:39 am #1044614Sure thing, thanks so much! Staging site is up here:
http://mikereinold2.wpengine.com/wp-admin (hosted on WPengine)
Same login. THANKS!
December 13, 2018 at 4:17 am #1044664Hi,
Thank you, I disabled the “Classic Editor” plugin to allow the “The editor has encountered an unexpected error” to show so I could test it, but the error doesn’t happen.
I tried a few ALB pages but it still didn’t happen, please try to see if you get the error.
Also the “Failed to load plugin” error that I last posted about was resolved once I realize my AD blocker was on and disabled it. Sorry, are you using a AD blocker and see any errors other than the text element “It seems you are currently adding some HTML markup or other special characters.” error?Best regards,
MikeDecember 14, 2018 at 12:20 am #1045070I am not using an ad blocker and do not have that 2nd issue you mention.
OK this is bananas. On my main site, I still get the editor error when I deactivate the “classic editor” plugin. However, you are right, when i log in to my staging site the error does not occur. I literally just made a copy of the entire website for the staging site, how could this be different?
I’m working with WP Engine on this now to see if they can help. I’ll send update when I have something. THANKS!
December 14, 2018 at 3:20 am #1045099Hi,
Yes, it is very strange, we look forward to hearing what WP Engine finds.Best regards,
MikeDecember 14, 2018 at 4:03 am #1045104Are you using legacy staging on WP Engine? That one is throwing a lot of errors on the front end which support can fix in a matter of minutes. They told me it’s a known issue with legacy staging.
December 14, 2018 at 2:07 pm #1045258Hi
@goldengate415, thanks that is a great tip.Best regards,
Mike -
AuthorPosts
- You must be logged in to reply to this topic.