Randy King

I am constantly getting this same annoyance as well on ALL of the sites where I have Yoast installed, both premium and free. What is causing this and how to stop it? I need to be able to quickly zoom in on my client sites and fix issues and when the Yoast menu is constantly showing up with the red dot to tell me this, it is REALLY annoying. This happens on sites where I make minor content adjustments on an existing page. This happens on sites where I do absolutely nothing except log in.

Is it the case that Automatic Updates to plugins could cause this? Just like these updates, why can’t Yoast just HANDLE IT automatically as well. This really slows down my day when I have to do this for bunches of sites.

It’s obviously been a problem for awhile because the canned support response isn’t even current with the Yoast interface. You can’t follow the instructions as they are presented.

C’mon guys – you’re better than this. Please fix this annoyance.

OK, I can certainly do that with the database. Yeah, very bizarre seeing as how this has worked 100% everywhere else. I will confirm in this thread after I fire up the SQL engine. ??

Whoops, I did not see this response until I got the notice that you were closing the thread. My apologies, I’m going to try the DEBUG option and let you know.

OK, thank you for the update. And just to note, it did not crash every website where I was using it – just 2 of them. Other sites continued working, but I disabled them all in the event that something would change and it would crash those as well. Looking forward to the update.

Thank you for the response, no javascript errors. No problem, I found another pop-up plugin that does not interfere with the Divi animation. All working now.

@kgwydir1 – Go into WP-Optimize/Cache on the WP left menu, click on the “Pre-Load” tab there, then disable scheduled cache preloading. If you Google the error message, you’ll see this has been discussed elsewhere.

Hello, @etiennep –

YES, that’s exactly what it was. Weird thing is that I had disabled that caching plugin when I went to Dreamhost’s WP hosting because they offer a server-side caching that’s more sophisticated. Somehow, the plugin got re-enabled and caused the problem, probably caching the cache. Now deleted, everything is working fine.

This post can serve as a place for someone else to have the DOH moment. ??

• This reply was modified 4 years, 6 months ago by Randy King.

**UPDATE** The stuck-in-draft problem seems to be related to a caching plugin. As I investigate further I will update this thread.

@arunmane – that is a different error from what I was experiencing. I recommend you start with the basics on this one…

— disable then completely remove the qsm plugin
— disable all other plugins
— re-load then enable the qsm plugin
If that works, then re-enable ONE of the other plugins at a time and check to see if any of them break things.

If you’re lucky, removing and re-loading qsm will solve the issue.

OK, thanks. Yeah, sure would be nice to be able to use all the tags when you implement that.

Hello again @fpcorso –

Bam! That’s exactly the problem. I had “Disable Visual Editor” set in my profile, and once I cleared it, the QSM editor launched and is working fine.

Thanks for going down that thread; I would never have hooked those two things together.

Before Divi, it was routine for me to start a new site and immediately turn off the visual editor so that it didn’t accidentally mangle my HTML and CSS that I put in most of my pages. Divi has made that all unnecessary, so leaving that unchecked is just fine.

Perhaps you can test for that during initialization and complain to the user if it is checked – will save some pain.

Thank you!
-=Randy

Yeah, I know – I was a premium customer in the past, and I never had this problem before. But I have not used it in over 9 months, so who knows. Here’s a couple of things that I have tried in addition to NO other plugins…
** Switched among PHP 7.0, 7.0 Fast CGI, 7.2, and 7.2 Fast CGI
** Different browsers: Firefox, Chrome, Edge

Click Here for a screenshot of the console.

Interesting that it seems to be objecting to TinyMCE – I am using the Divi theme from Elegant Themes with its own editor, so the default WP editor is not used.

@shelob9 –

Josh – I’ll look again in the console and submit via the standard support channel. When we find it, I’ll report back here for others.

-=Randy

Sorry, not an answer Roland, but a testimonial that I have exactly the same problem and reluctantly had to just deactivate and uninstall Comet Cache. Some time last year there was a discussion about caching in general causing problems with Caldera forms.

I am hosted on Dreamhost.