Suppress presistent errors: ex. Broken Dependencies, wp-auth-check on WP Engine

+1

Thanks for the report. This is something you should report to WPEngine because, as QM shows, this is actually a broken dependency.

John, I’m totally aware this is an accurate error/warning QM is showing. The issue is that the cause is known and Deliberate. Here WPE throttles the heartbeat to reduce load. I imagine that’s not the only instance anyone has come across where an error or warning is persistently shown and _delibrately_ caused.

It would seem useful to me to have a filter In QM to surpress specific persistent error messages, like this, on a site by site basis. I’m not saying QM should ignore anything by default, just user have a way to surpress errors on their own in cases like this.

I’m totally fine with a “no, don’t want to add that” for performance/philosophical/whatever reason, just wanted to be clear what is was suggesting.

Thanks for the message, Jon.

To clarify what I meant in my earlier reply, the issue is that deregistering a script (heartbeat in this example) will break all of its dependent scripts, and is not the correct way to remove a dependency, hence the big red message from QM. I think that adding a filter that allows such a message to be hidden isn’t a good idea because it allows for a broken implementation to be hidden.

A better approach in this particular situation is for WPEngine to override the heartbeat script with its own JavaScript file that no-ops all of the Heartbeat methods.

TY John!

A better approach in this particular situation is for WPEngine to override the heartbeat script with its own JavaScript file that no-ops all of the Heartbeat methods.

I love this idea. It’s a much better way of doing things. And since I work at WPE, I’ll be opening up a bug internally to attempt to fix this for our users. ??

Can’t really give a timeframe —?nor do I know if the engineering team in charge of our functionality plugin will go for it — but I’ll do my best to keep on top of this.

TY Cosper!

Hey Jason,

Any update on that solution from your team?

I just installed Query Monitor and see this error. Has any progress been made on WP Engines behalf?

• This reply was modified 7 years, 7 months ago by mikegraf.

I’d love to see WP Engine fix this bug for sure.