Closed DonaBumgarner closed 4 years ago
I'm having the same issue, exactly. It's been happening since 5.0 and 5.0.1
I've tried in Chrome and Firefox with the same result, and with all plugins disabled by Yoast SEO 9.2.1
WordPress version: 5.0.1 Yoast SEO version: 9.2.1 Gutenberg plugin version: Classic Editor plugin version: 1.3 Relevant plugins in case of a bug: This occurs even with all plugins disabled.
I followed all the advice/checks/tests in your troubleshooting article before posting.
I am also experiencing the same issue and performed all recommended troubleshooting.
Same issue. SEO Metabox is empty. Inspecting shows all inputs are set to type "Hidden".
Thanks for reporting this issue. Unfortunately, we do not have enough information to reproduce this problem. Please follow these guidelines to provide us with more relevant information.
It might be helpful if you can share a screenshot of the javascript console. I also need an overview of the plugins and themes you are using.
Thank you.
We also have release version 9.3 in the meanwhile. I recommend to update to this version. This might solve the issue. If not, please let me know.
same issue here. Wordpress 5.0.2 and yoast 9.3
@andizer We have followed all of the steps listed in the "How to write a good bug report" guide. The OP has the format requested, we've included versions, and I added screenshots showing both the issue, and that I was using the troubleshooting method recommended with a default theme and all plugins except Yoast disabled.
There are no errors in the JavaScript console. As I showed in the screenshot above, the input type on the missing fields is set to hidden.
@dudabueno @cookienameddesire (my god, that username cracks me up), @rolanddenzel @DonaBumgarner can you all use the Chrome inspector on your post edit screen and confirm your input types are set to "hidden" as well?
I got the same problem after updating from 9.3 to 9.4 on Wordpress 4.9.9. As requested by @andizer, I attached a screenshot from the Crome JavaScript console.
With Yoast 9.3, the JavaScript Console does not report any exceptions.
Same issue for me. The "Content Optimization" panel/tab is blank, but the other tabs (Social & Advanced) are working fine.
This happened after updating to Yoast SEO ver. 9.4 yesterday from 9.3. I didn't have any issues before the update.
I'm running Wordpress 5.0.3 (auto-updated today) using Hitmag Theme, again, I didn't have any issues before the update.
Here's part of the code as requested by @TheFeloniousMonk
Another small issue is the Yoast SEO Posts Overview is not loading. The Yoast icon just keeps spinning.
edited: I also have the same errors as posted by @Peroks-01
@andizer so we've confirmed at this point that the fields are being generated with input type "hidden".
@dudabueno @cookienameddesire (my god, that username cracks me up), @rolanddenzel @DonaBumgarner can you all use the Chrome inspector on your post edit screen and confirm your input types are set to "hidden" as well?
@TheFeloniousMonk Can you give me a couple of steps to do this? I'm not familiar with the tool. In Chrome I'm going to View -> Developer -> Developer Tools and loading my post edit view. What are the next steps to view the input types code? I'm not seeing anything that looks like your image, so I think I'm missing a step.
@andizer Thanks to the other folks posting their information in this thread, it looks like you have here everything you are looking for - Java Errors, console inspector information, theme isolation, and it the issue is still occurring with v. 9.4 of the plugin. See @MikeG40 's post above for most recent configuration with all the updates - still occurring. If you need additional specific information, please let us know. We are all eager to get this plugin working for us again.
@DonaBumgarner if you right click on the Yoast metabox and select 'Inspect', it should bring up the Chrome Inspect view with that box as the focus.
@DonaBumgarner if you right click on the Yoast metabox and select 'Inspect', it should bring up the Chrome Inspect view with that box as the focus.
Thank you! And thanks for your help gathering data for this issue. @TheFeloniousMonk
Here is my Inspector log, also showing "hidden".
Updated to Wordpress ver 5.0.3 (my auto-update is turned on).
Still the same issues, still hidden.
Same issue here with Wordpress 4.8.8, Woocommerce and Yoast 9.2.1 Inputs are generated but with type hidden. If changed in inspector to text, they are populated and work.
Again, we're not seeing javascript errors in the output (Chrome)
content.js:2 [Violation] Added synchronous DOM mutation listener to a 'DOMNodeInserted' event. Consider using MutationObserver to make the page more responsive.
Navigated to https://www.paint-paper.co.uk/wp-admin/post.php?post=40711&action=edit
load-scripts.php?c=0…lupload&ver=4.8.8:9 JQMIGRATE: Migrate is installed, version 1.4.1
5
[Violation] Forced reflow while executing JavaScript took <N>ms
16
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
load-scripts.php?c=0…lupload&ver=4.8.8:2 [Violation] 'DOMContentLoaded' handler took 2118ms
2
tinymce.min.js?ver=4603-20170530:13 [Violation] Avoid using document.write().
tinymce.min.js?ver=4603-20170530:4 [Violation] 'load' handler took 427ms
plugin.min.js?wp-mce-4603-20170530:1 [Violation] 'setTimeout' handler took 161ms
tinymce.min.js?ver=4603-20170530:3 [Violation] 'setTimeout' handler took 58ms
shim.latest.js:1 [Violation] Avoid using document.write().
load-scripts.php?c=0…p-embed&ver=4.8.8:5 [Violation] 'setTimeout' handler took 174ms
In some way, without updating anything, it's back! Gonna work on the optimization of a bunch of articles and will let you know if it's all good.
Still seeing the issue here.
Seems to be working, I've edited 4 articles and managed to get it optimized based on the suggestions by Yoast. The Yoast Overview on my dashboard seems to be working too.
That's before I've edited it for optimization.
I'm seeing the problem with:
It appears to be theme-independent as it's a problem with the current Dandelion theme and the WordPress Twenty Nineteen theme.
Here's an image with the JavaScript errors I'm seeing:
and as reported by others, all the fields are there, just hidden:
It looks like it is a persistent problem. I installed a new wordpress on another domain, 5.0.3.. the "Content Optimization" tab is blank again.
Here are the installed plugins and theme. Wordpress 5.0.3 Theme: Awaken 2.2.0
Active Plugins: Under Construction 3.31 W3 Total Cache 0.9.7 Wordfence Security 7.1.20 Yoast SEO 9.4
Hi all, and thank you all for your contribution.
This proves to be a difficult issue to tackle, as you all seem to have different variables in your installations. So far, we have been unable to reproduce the issue on our testing machines.
Just to make one thing clear: the input fields that a lot of you mention, from the wpseo-meta-section-content
div, are meant to be hidden. This can be checked in a working installation as they are invisible there as well.
@MikeG40 you seem to have had this issue on one of your installations, but 4 days later the issue seems to have disappeared according to your messages. As you say you have not updated our plugin in the meantime, nor your WordPress installation, something else must have changed. Would you mind thinking back to those days and see if you can recall anything that might have influenced this? Think about:
As for the others who experience this issue, to be able to fix this we need to be able to reproduce this. Any information that you have that might help, please let us know. Based on the screenshots provided it looks like the wpseo-metabox-root
element is either missing, hidden or overwritten. If somebody with a working and a non-working installation could verify this we might have something to look for.
On a non-working installation, I see an empty wpseo-metabox-root div:
On a working installation, I see a non-empty wpseo-metabox-root div:
@Djennez nothing major actually. Haven't updated any browsers as I have a bunch of websites opened and I don't want to re-open them again when I shut down. So it's on a sleep-ON cycle for more than a week already.
To answer your questions: Updates or changes to your browser - none, haven't updated the browsers.
Settings within your WordPress installation that have changed None on my 1st website, didn't change the theme or anything. The last update of the theme was January 2, so not much for the theme.
Something about your hosting environment that has changed There was no updates with my hosting. Apache/Php versions are still the same as months ago.
New, deleted or updated other plugins in that WordPress installation This I couldn't remember but I think I did updated all my active plugins and removed non-active plugins. I'll list below my current plugins for 3 websites.
these are the plugins and themes for 3 websites currently on my hosting.
1st website originally has the problem but now has been somehow fixed
wordpress: 5.0.3 theme: HitMag 1.2.1 Active plugins: Ad Inserter 2.4.8 AddToAny Share Buttons 1.7.33 Akismet Anti-Spam 4.1 All-in-One WP Migration 6.83 AMP 1.0.2 Contact Form 7 5.1.1 File Manager 5.0.4 Flamingo 1.9 Forget About Shortcode Buttons 2.1.2 Glue for Yoast SEO & AMP 0.4.3 Jetpack 6.9 MetaSlider 3.10.3 Redux Framework 3.6.15 Simple Custom CSS 4.0.1 Social Icons Widget by WPZOOM 3.0.13 Under Construction 3.31 W3 Total Cache 0.9.7 Wordfence Security 7.1.20 Yoast SEO 9.4
2nd website new install - not working
wordpress: 5.0.3 theme: Awaken 2.2.0 Active plugins: AddToAny Share Buttons 1.7.33 All-in-One WP Migration 6.83 AMP 1.0.2 Contact Form 7 5.1.1 Flamingo 1.9 Glue for Yoast SEO & AMP 0.4.3 Jetpack 6.9 Redux Framework 3.6.15 Social Icons Widget by WPZOOM 3.0.13 Under Construction 3.31 W3 Total Cache 0.9.7 Wordfence Security 7.1.20 Yoast SEO 9.4
3rd website just installed today - Yoast SEO working perfectly
wordpress: 5.0.3 theme: Twenty Seventeen 1.7 Active plugins: Ad Inserter 2.4.8 AddToAny Share Buttons 1.7.33 All-in-One WP Migration 6.83 AMP 1.0.2 Contact Form 7 5.1.1 Flamingo 1.9 Glue for Yoast SEO & AMP 0.4.3 Jetpack 6.9 Redux Framework 3.6.15 Social Icons Widget by WPZOOM 3.0.13 Under Construction 3.31 W3 Total Cache 0.9.7 Wordfence Security 7.1.20 Yoast SEO 9.4
There is a new update for Yoast SEO 9.5 but I'm reluctant to update it..
I hope this helps.
In my build, I used the debugging method recommended, with default theme and all plugins except Yoast deactivated, and still had the issue.
Is there a PHP version issue maybe? I'm running 7.1 on my server.
I should have checked before installing all the other plugins..
I'm having the same issue. It happend today, after updating Yoast SEO from 9.4 to 9.5. Returning Yoast SEO 9.4 from backup didn't solve the problem
WordPress version: 5.0.3 Yoast SEO version: 9.4 and 9.5
Same issue on WP 5.0.3 and Yoast 9.5 on two separate websites.
So, I am now looking to get some more variables to see which ones match between all installations with issues.
Would you mind running the following on a website with the issue:
Dashboard -> Health Check -> Debug Information -> show copy and paste field
<details>
<summary>Expand</summary>
Replace only this text with your output.
</details>
(this will create a collapsible block, so we don't have to scroll miles to get to other posts)
Hoping to get enough data to pinpoint this problem. Any other errors (from the javascript console or server errors) are welcome too. Please create a second collapsible block for those.
Here's our Health Check Debug Information:
Here is our Health Check report
Here you are
@Djennez is that enough data for you or do you need more ?
(just trying to not let this thread die... for lack of feedback to you)
This problem appears to be related to Conflict when Classic Editor plugin and Gutenberg are activated · Issue #11423 · Yoast/wordpress-seo. When the Classic Editor plugin is enabled, the problem occurs (when using "Edit (Classic Editor)").
On my site, reverting to Yoast SEO 9.3 restores the functionality. Using Yoast SEO 9.4, 9.5 or 9.6 has the problem. So the problem may have originated between versions 9.3 and 9.4.
On my site, reverting to Yoast SEO 9.3 restores the functionality.
Same here. But in my case, Gutenberg is not a factor. I'm still on WP 4.9.9 and have never installed the Gutenberg plugin.
So there is one thing which has not been tried before, as far as I can tell by this thread: deactivating all other plugins except for Yoast SEO (and the classic editor plugin, if relevant).
I was unable to locate plugins or variables from all the logs which are the same for all the websites, but it might still be an issue with plugins that use the same functionality. If you experience this issue, can you try disabling other plugins to see if this issue persists? If disabling all plugins fixes the issue, please re-enable the plugins one by one untill you run into the issue again.
In my case, the problem is this plugin:
WP Log Viewer, https://wordpress.org/plugins/wp-log-viewer/
When I deactivate WP Log Viewer, the Yoast Snippet Preview works fine and the exceptions disappear from the JavaScript Console.
@Djennez I tested with all other plugins deactivated and still had the issue.
@Djennez I tested with all other plugins deactivated and still had the issue.
Same here...
@Djennez I tested with all other plugins deactivated and still had the issue.
I also have the issue since some days.
I have the same problem with the plugin: WP Log Viewer, https://wordpress.org/plugins/wp-log-viewer/
When deactivated, Yoast works (after I empty cache), but my blog does not show up.
So I have to -deactivate (blog is down) while I use the Yoast plugin, -save, -then reactivate Log Viewer (so my blog will show up again) -and Yoast snippet disappears.
Any updates on this issue with WP Log Viewer??
Has there been any updates to what may be causing the issue? I have recently gone through and deactivated what plugins I could (some I am unable to deactivate as they are critical to the functionality of my website's front end). None have had any effect on the usability of the Yoast plugin. I am still not on Gutenberg. If it helps, I am also attaching the console errors I've just grabbed.
Hello. I have the same prblem.
WooCommerce version: 3.5.5 WordPress version: 5.1 Apache/2.4.25 PHP version: 7.2.13 WooCommerce database version: 3.4.6
Classic Editor – 1.4 Contact Form 7 – 5.1.1 Post SMTP – 1.9.8 Product Feed PRO for WooCommerce – 4.9.6 WooCommerce Additional Variation Images Gallery – 1.1.21 Woocommerce XML Feeds – 3.5.5 Booster for WooCommerce – 4.2.0 WooCommerce Pay for Payment – 2.0.12 Zásilkovna Shipping Method – 0.1 WooCommerce – 3.5.5 WooSidebars – 1.4.5 Yoast SEO – 9.7 YITH WooCommerce Wishlist – 2.2.8
Flatsome theme 3.8.1
All plugins except Yoast and Woocommerce was deactivated before without result.
Here is the video, where you can see, that metabox is appeares on the first 1 sec., and after that makes blank: https://www.loom.com/share/feae5494aab94c92aa5662bcf3b16fb0
If you have classic editor installed in your plugin disable it. It worked for me
Thanks, Yudee01!
I have noticed that issue connected with browser. The issue is only visible in Chrome browser. In Firefox and Safari everything works fine.
Thanks, Yudee01!
I have noticed that issue connected with browser. The issue is only visible in Chrome browser. In Firefox and Safari everything works fine.
I'm seeing this problem in both the current version of Chrome (73) AND Firefox (65) AND Safari (12). So I thinks it's something other or more than just the browser.
I tried in Chrome (my daily driver), Firefox, and Edge with the same results.
Please give us a description of what happened.
After a recent round of updated (both WP and plugins) I noticed that the Yoast content optimization window in my post editor is blank. This seems to be identical to an issue posted some months ago in the WP forum (https://wordpress.org/support/topic/yoast-plugin-is-not-working-on-wordpress-4-9-8/) which was indicated to have been fixed with Yoast version 8.0. However, I'm using Version 9.2.1 and seeing the problem again (another user posted in the WP forum thread that he is also seeing the issue with 9.2.1.).
Please describe what you expected to happen and why.
How can we reproduce this behavior?
Technical info
Used versions