Multiple JavaScript Errors with Classic Editor
-
Hey,
So since 6.3 I’ve had a lot of JavaScript errors coming from your classic.js – something to do with React 18 vs 17.
But it’s actually caused the server to have the “too many requests” issue at the same time.
I am using the official “Classic Editor” plugin from WordPress, if that helps.
Here are the screenshots of some of the errors:
Hopefully that’s enough for us to work together to help fix this.
Thanks,
FJ
-
Hello @fibrojedi,
Thank you for contacting Rank Math support.
It seems like you are using a very old version of our plugin on your site. Please update it to the latest version and the issue should be fixed: https://rankmath.com/changelog/free/
If the issue persists on the latest version, it would seem like a conflict with one of the plugins or the theme you are using.
To determine that, please follow this troubleshooting guide:
https://rankmath.com/kb/check-plugin-conflicts/Here is a video you can follow as well: https://www.youtube.com/embed/FcIWRhcUP2c
Only the site admin would know and your users won’t be affected by this troubleshooting.
Let us know how that goes. Looking forward to helping you.Heya,
Actually, it’s the opposite: I’m on your 1.1.0 beta, so I’ll deactivate that and re-add the current “Live” one, and hope that all the data remains in-tact.
Thanks,
FJ
Okay, so I found the “rollback” feature and used that fine.
However, I am still getting the the ReactDOM error
Warning: ReactDOM.render is no longer supported in React 18. Use createRoot instead.
which is being triggered by
seo-by-rank-math/assets/admin/js/classic.js
But I’m not getting “too many requests” so that’s the biggest thing. What can I do to fix the React error, please?
Thanks.
Hello @fibrojedi,
That file you mentioned doesn’t use this function from React so it wouldn’t throw that error, at least not in the latest version of the plugin.
First make sure that you are running version 1.0.122 and if the issue persists, please share a screenshot of the same so we can check in more detail.
Thank you.
Hey,
Yep, I’m on 1.0.122 – but just so I can prove it:
Hope this helps and have a good weekend,
FJ
Just to confirm – deactivating Rank Math removes the errors above. That’s not to say there isn’t a conflict, but there is an issue we can work together to resolve.
Thanks.
Hello @fibrojedi,
Can you please let us know which specific page are you on where the console error is showing or is the error appearing everywhere?
Also, please clear your website cache and head over to your WordPress > Rank Math > Status & Tools > Database Tools and click on the button “Remove Transients”. See if this improves the situation.
Lastly, if the issue persists, please deactivate and delete the Rank Math plugin and install a fresh one.
Looking forward to helping you with this one.
Hey,
- The error only seems to be appearing on post.php – so adding and editing posts/pages. This makes sense given the error relates to your /admin/js/classic.js – at least according the Developer Tools.
- Weirdly, I also thought of the transients and cleared those yesterday, but there was no change.
→ I use a CDN for caching so I don’t have a local cache anymore, and the admin panel is blacklisted from cache anyway. (see below about localhost too)
→ I have an object cache, but as that’s mostly SQL queries it would have no bearing on specific files.
→ I re-deleted transients (where was one!). - The issue is still there, but won’t deleting the plugin cause me to lose titles/social tags per post etc?
Another thing to point out is that I get these errors in a local version of the site too – one with far fewer plugins (and no cache or CDN)
Warning: ReactDOM.render is no longer supported in React 18. Use createRoot instead. Until you switch to the new API, your app will behave as if it's running React 17. Learn more: https://reactjs.org/link/switch-to-createrootreact-dom.js:73:32 React 3 value https://localhost/wp-content/plugins/seo-by-rank-math/assets/admin/js/classic.js:1 (Async: setTimeout handler)
value https://localhost/wp-content/plugins/seo-by-rank-math/assets/admin/js/classic.js:1 runHooks https://localhost/wp-includes/js/dist/hooks.js:395 <anonymous> https://localhost/wp-content/plugins/seo-by-rank-math/assets/admin/js/classic.js:1 jQuery 28 <anonymous> https://localhost/wp-content/plugins/seo-by-rank-math/assets/admin/js/classic.js:1 jQuery 10 <anonymous> https://localhost/wp-content/plugins/seo-by-rank-math/assets/admin/js/classic.js:1 <anonymous> https://localhost/wp-content/plugins/seo-by-rank-math/assets/admin/js/classic.js:1I hope _something_ in here helps!
Thanks,FJ
- This reply was modified 1 year, 3 months ago by Fibro Jedi.
Hello @fibrojedi,
No, reinstalling a new copy of the plugin will not remove all your metadata from Rank Math since all settings data are saved to your database.
You can always take a backup before disabling and deleting the plugin.
With that said, please check all the features of Rank Math if it’s working properly, the message is just a warning and shouldn’t cause any major issues with Rank Math features.
Looking forward to helping you. Thank you.
A new install didn’t get rid of it. But at least I don’t have the “too many requests” thing going anymore.
Interesting that uninstalling Rank Math doesn’t remove its data, though. I’m not about to change, but most plugins do delete their data after a complete uninstall.
Re: The React error, I’ve been trying to reduce errors (not warnings) site-wide. If yours was just a “yellow” advisory note in Dev Tools I would have ignored it. Anyway, thanks for your help – the core issue (too many requests) is sorted, even if there’s no actual solution for the react error.
Thanks for helping.
FJ
Hello @fibrojedi,
For completely uninstalling, please follow this guide:
https://rankmath.com/kb/uninstall/Please don’t hesitate to get in touch with us if you have any other questions.
Thank you.
I think I’ll just put up with the last error. I have a 1200+ post website and the mere thought of having to restore the RankMath data and it possibly going wrong is too much!
I’ll just leave that React warning in place. As I said, the main thing is the “too many requests” error has gone. So this ticket can be actually seen as resolved, rather than just marked as resolved.
Thanks again!
Hello @fibrojedi,
We are glad that the main issue has been resolved.
Don’t hesitate to get in touch with us if you have any other questions.
- The topic ‘Multiple JavaScript Errors with Classic Editor’ is closed to new replies.