Title: Yoast Plugin Bug
Last modified: December 5, 2018

---

# Yoast Plugin Bug

 *  Resolved [sniper007](https://wordpress.org/support/users/sniper007/)
 * (@sniper007)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/yoast-plugin-bug/)
 * Hello,
 * I had a problem that Readability Analysis and Focus Keyphrase panels would not
   load any more with the last version of Yoast what ever I tried to solve..
 * I downgraded the plugin step by step till I found that the last plugin version
   without this bug is version 9.1 so I stick with it.
 * Please fix this bug as soon as possible as I want to update to the last version.
 * Thanks..

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

 *  [sv1cec](https://wordpress.org/support/users/sv1cec/)
 * (@sv1cec)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/yoast-plugin-bug/#post-10954666)
 * I have the same problem, Content Optimization tab shows nothing with the latest
   version of Premium!!!
    -  This reply was modified 7 years, 5 months ago by [sv1cec](https://wordpress.org/support/users/sv1cec/).
 *  [sv1cec](https://wordpress.org/support/users/sv1cec/)
 * (@sv1cec)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/yoast-plugin-bug/#post-10958061)
 * Sniper007, are you by any chance using Pods – Custom Content Types and Fields
   plugin in your site?
 *  [Jerlyn](https://wordpress.org/support/users/jerparx/)
 * (@jerparx)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/yoast-plugin-bug/#post-10958622)
 * [@sniper007](https://wordpress.org/support/users/sniper007/)
    Can you please 
   provide us with the error message you are getting on your console when you click
   on the blank meta box? This KB article explains how to do so: [How to find JavaScript errors with your browser’s console?](https://kb.yoast.com/kb/how-to-find-javascript-errors-with-your-browsers-console/)
 * Also, can you confirm if you are using WPML? ​There was a [reported bug between Yoast SEO 9.2 and WPML](https://github.com/Yoast/wordpress-seo/issues/11646).
   The WPML developers have recently released a new version which includes the fix
   for this issue.
 * Can you confirm if updating your WPML plugin resolves the issue?
 * ​If you are not using WPML, can you confirm if you have the latest WordPress (
   4.9.8) and Yoast SEO (9.2.1) versions? When you update them to the latest, does
   the issue resolve?
 * [@sv1cec](https://wordpress.org/support/users/sv1cec/)
    As a Premium customer,
   you may send an email directly to [support@yoast.com](https://wordpress.org/support/topic/yoast-plugin-bug/support@yoast.com?output_format=md)
   so we can assist you further.
 *  [sv1cec](https://wordpress.org/support/users/sv1cec/)
 * (@sv1cec)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/yoast-plugin-bug/#post-10958674)
 * I have done that. And I figured out what the problem was. The plugin Pods – Custom
   Content Types and Fields causes the problem, if you are running their latest 
   version. If you run the previous one, everything is fine.
 *  [Scott Kingsley Clark](https://wordpress.org/support/users/sc0ttkclark/)
 * (@sc0ttkclark)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/yoast-plugin-bug/#post-10958739)
 * [@jerparx](https://wordpress.org/support/users/jerparx/) Please send the Pods
   team access to Yoast premium for testing purposes so we can investigate this 
   compatibility issue. I hit up Taco too but hopefully one of ya’ll can help out
   here.
 * E-mail is scott at pods.io
    -  This reply was modified 7 years, 5 months ago by [Scott Kingsley Clark](https://wordpress.org/support/users/sc0ttkclark/).
 *  [Taco Verdonschot](https://wordpress.org/support/users/tacoverdo/)
 * (@tacoverdo)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/yoast-plugin-bug/#post-10959231)
 * Done, [@sc0ttkclark](https://wordpress.org/support/users/sc0ttkclark/)!
    -  This reply was modified 7 years, 5 months ago by [Taco Verdonschot](https://wordpress.org/support/users/tacoverdo/).
      Reason: typo
 *  [Scott Kingsley Clark](https://wordpress.org/support/users/sc0ttkclark/)
 * (@sc0ttkclark)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/yoast-plugin-bug/#post-10959393)
 * Thanks Taco! Our team is now on the case, we found at least one issue that is
   already resolved in our code for this release. Doing some more checking to see
   if there are any other remaining issues.
 * Seems like plugin authors are all defensively programming for Gutenberg / WP 
   5.0 and our tweaks are conflicting/overlapping in some places 🙂 fun times!
 *  [sv1cec](https://wordpress.org/support/users/sv1cec/)
 * (@sv1cec)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/yoast-plugin-bug/#post-10959892)
 * I understand “fun times” but suggesting to a paid customer to upgrade to WP5 
   in order to solve this issue, while on the same time your own documentation suggests
   that we should wait for some time before upgrading to WP5, is a sorry approach.
   That’s what your support suggested and I find it hard to shallow. Like I find
   it hard to understand how your support can suggest to shut down an active site,
   by deactivating all plugins and non-WP themes, in order to find out what is causing
   this issue.
 * While I understand what you are all going through with the update of WP, such
   an approach is not acceptable for a production site. Thank God, we also have 
   a development site in which we can test things,
 * [@tacoverdo](https://wordpress.org/support/users/tacoverdo/), if you are part
   of the management team in Yoast, your support leaves a lot to be desired. If 
   you are not, I would appreciate an email address for your top management.
 * Thank you!!!
 *  Plugin Support [Michael Tiña](https://wordpress.org/support/users/mikes41720/)
 * (@mikes41720)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/yoast-plugin-bug/#post-10981863)
 * [@sv1cec](https://wordpress.org/support/users/sv1cec/)
 * If you have an active subscription for any of our premium plugins, please do 
   contact us directly so we can help check on the issue and provide personalized
   support for you — [https://kb.yoast.com/kb/support/#premium](https://kb.yoast.com/kb/support/#premium)
 *  Plugin Support [Michael Tiña](https://wordpress.org/support/users/mikes41720/)
 * (@mikes41720)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/yoast-plugin-bug/#post-11010494)
 * No further response, setting this to closed to keep the overview going.

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

The topic ‘Yoast Plugin Bug’ 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/)

 * 10 replies
 * 6 participants
 * Last reply from: [Michael Tiña](https://wordpress.org/support/users/mikes41720/)
 * Last activity: [7 years, 5 months ago](https://wordpress.org/support/topic/yoast-plugin-bug/#post-11010494)
 * Status: resolved