Title: Yoast Editor Not Loading &#8211; JS Console Errors
Last modified: November 19, 2023

---

# Yoast Editor Not Loading – JS Console Errors

 *  Resolved [zen10](https://wordpress.org/support/users/zen10/)
 * (@zen10)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/yoast-editor-not-loading-js-console-errors/)
 * The editor won’t load and throws the JS errors below.
 * I’ve disabled all plugins and reverted to the default 2024 theme in a staging
   area and this still occurs in the /wp-admin/ when editing any page.
 * What should I try next?
 * [Error] TypeError: Object.hasOwn is not a function. (In ‘Object.hasOwn(e,n)’,‘
   Object.hasOwn’ is undefined)
   pe (classic-editor.js:384:18848)(anonymous function)(
   classic-editor.js:384:18951)a (classic-editor.js:1:115)(anonymous function) (
   classic-editor.js:431:1800)a (classic-editor.js:1:115)(anonymous function) (classic-
   editor.js:522:5397)a (classic-editor.js:1:115)(anonymous function) (classic-editor.
   js:529:4975)a (classic-editor.js:1:115)(anonymous function) (classic-editor.js:
   1:904)Global Code (classic-editor.js:1:914)[Error] TypeError: window.yoast.initEditorIntegration
   is not a function. (In ‘window.yoast.initEditorIntegration(e)’, ‘window.yoast.
   initEditorIntegration’ is undefined)(anonymous function) (post-edit.js:29:3064)
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fyoast-editor-not-loading-js-console-errors%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 8 replies - 1 through 8 (of 8 total)

 *  Thread Starter [zen10](https://wordpress.org/support/users/zen10/)
 * (@zen10)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/yoast-editor-not-loading-js-console-errors/#post-17213753)
 * Update – Only affects Safari, Chrome is fine so I don’t need a response, this
   workaround is fine.
 *  Plugin Support [Maybellyne](https://wordpress.org/support/users/maybellyne/)
 * (@maybellyne)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/yoast-editor-not-loading-js-console-errors/#post-17216118)
 * Thanks for using the Yoast SEO plugin, [@zen10](https://wordpress.org/support/users/zen10/)
   and for sharing your workaround.
 *  [oliviersia09000](https://wordpress.org/support/users/oliviersia09000/)
 * (@oliviersia09000)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/yoast-editor-not-loading-js-console-errors/#post-17262085)
 * I have the exact same problem on Microsoft Edge.
   I can’t change browser because
   it’s the client’s browser.I have cleared all cached files and images on the client’s
   browser.I have deleted cookies from the affected website on the customer’s browser.
   What can I do ?Sincerely
 *  [iskisbzh](https://wordpress.org/support/users/iskisbzh/)
 * (@iskisbzh)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/yoast-editor-not-loading-js-console-errors/#post-17262154)
 * Hello,
   Same error on firefox linux.Object.hasOwn is not a function block-editor.
   js:419:5164This ticket is not resolved
 *  [oliviersia09000](https://wordpress.org/support/users/oliviersia09000/)
 * (@oliviersia09000)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/yoast-editor-not-loading-js-console-errors/#post-17271210)
 * up
 *  [oliviersia09000](https://wordpress.org/support/users/oliviersia09000/)
 * (@oliviersia09000)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/yoast-editor-not-loading-js-console-errors/#post-17272225)
 * Hello,
   With update to 21.7 same problem.
 *  [rtpHarry](https://wordpress.org/support/users/rtpharry/)
 * (@rtpharry)
 * [2 years, 5 months ago](https://wordpress.org/support/topic/yoast-editor-not-loading-js-console-errors/#post-17273815)
 * This is affecting my client as well.
 * Exact same error log as OP.
 * I’ve installed WP Rollback, and rolled back through each point release from 21.7
   back to 21.1 where it started working again. (Using a ctrl-r refresh on the site,
   and with the dev tools open, which I assume flushes the browser cache like Chrome)
 * Their mac is a bit older, running macOS 11.78, and its in Safari 14.1.3.
 * We tested and with 21.7 it was working on their Chrome browser, but it isn’t 
   their main driver so I needed to find an immediate solution for them.
 * On my Macbook Pro / macOS 13.5 / Safari 16.6 it was working fine on 21.7, I didn’t
   test it as I was rolling each version back.
 * Hopefully this helps you dig into the actual issue?
    -  This reply was modified 2 years, 5 months ago by [rtpHarry](https://wordpress.org/support/users/rtpharry/).
 *  [rtpHarry](https://wordpress.org/support/users/rtpharry/)
 * (@rtpharry)
 * [2 years, 5 months ago](https://wordpress.org/support/topic/yoast-editor-not-loading-js-console-errors/#post-17273853)
 * For others with this issue, I have started my own thread because this one is 
   marked as resolved and also Yoast staff haven’t been acknowledging it since the
   first reply:
 * [https://wordpress.org/support/topic/yoast-panel-not-displaying-on-safari-14/](https://wordpress.org/support/topic/yoast-panel-not-displaying-on-safari-14/)

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘Yoast Editor Not Loading – JS Console Errors’ is closed to new replies.

 * ![](https://ps.w.org/wordpress-seo/assets/icon-256x256.gif?rev=3419908)
 * [Yoast SEO - Advanced SEO with real-time guidance and built-in AI](https://wordpress.org/plugins/wordpress-seo/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordpress-seo/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordpress-seo/)
 * [Active Topics](https://wordpress.org/support/plugin/wordpress-seo/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordpress-seo/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordpress-seo/reviews/)

 * 8 replies
 * 5 participants
 * Last reply from: [rtpHarry](https://wordpress.org/support/users/rtpharry/)
 * Last activity: [2 years, 5 months ago](https://wordpress.org/support/topic/yoast-editor-not-loading-js-console-errors/#post-17273853)
 * Status: resolved