Support » Plugin: Yoast SEO » Internet Explorer won’t render editor icons or text content if Yoast enabled

  • Resolved rklrkl

    (@rklrkl)


    We’re running WP 5.0.1 (and have tried downgrading to WP 4.9.9 too) with any of the last 3 releases of Yoast SEO plugin (up to and including 9.2.1).

    Two of our client sites have missing backend editor icons and text content (we have Classic Editor installed, so it’s TinyMCE we use) when the Yoast SEO plugin is enabled in Internet Explorer 11 (it’s fine on Firefox and Chrome, which probably rules out our install or other plugins clashing).

    If we disable the Yoast SEO plugin and reload the post editor page in IE 11, the editor icons re-appear, as does the text in the main editing aera. The finger definitely points towards the Yoast SEO plugin and its support for IE 11.

Viewing 5 replies - 1 through 5 (of 5 total)
  • I’ve got a couple of clients also reporting this issue. It’s only in IE11, Edge and other browsers are all fine. Have disabled and re-enabled all plugins and can confirm that the cause is definitely Yoast SEO.

    Unfortunately the clients are not able to upgrade their browser in their office so they are stuck with IE11.

    rklrkl

    (@rklrkl)

    Just a note that WP 5.0.2 with Yoast SEO 9.3 enabled still breaks both the TinyMCE *and* Gutenberg editors – they both lose their editor icons and all the text in their main editing areas when in visual mode.

    Now another user in this thread has confirmed the bug, this has become quite a serious issue for all IE11 users. Sadly, our clients don’t want to or can’t switch away from IE11, so we’ve actually had to disable the Yoast SEO plugin on their sites until this rather major bug is fixed!

    There’s an open ticket about it on the Yoast SEO GitHub repository (which I’ve also commented on), so it looks like they are aware of this issue: https://github.com/Yoast/wordpress-seo/issues/11733

    Plugin Support Md Mazedul Islam Khan

    (@mazedulislamkhan)

    Thanks for bringing this to our attention. A bug report has already been submitted here and our development teams are well aware of this. This means will investigate the issue further.

    If you have more information about the issue, please do feel free to submit them over at the GitHub issue directly.

    Plugin Support jerparx

    (@jerparx)

    Closed this thread. Please follow the Github link to monitor the status of the issue. You can leave a comment to the GH report so you get notified whenever there’s an update.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.