SGO Heartbeat Triggering Javascript Error

Hello @generosus,

I was able to recreate the reported error on my personal site and forwarded the information to our developers for further review.

Best regards,
Dimo

Hi @dimodi,

That’s great. Looking forward to the fix.

Thank you!

Hello @generosus,

Our developers reviewed the case in details, but I am afraid that there isn’t really a feasible solution.

The Query Monitor plugin relies on the Heartbeat functionality and when disabling it, the plugin will naturally return an error. While the solution provided in your link will hide the displayed error, it will not address it, leaving the risk for Query Monitor or parts of it functionality to stop working.

That is why we decided against applying a fix like this. It’s more of a workaround that might potentially lead to other issues, instead of a direct fix.

What I can offer you at this point, is to have the native WordPress Heartbeat functionality enabled, when you use the Query Monitor plugin.

Best Regards,
Tsvetan

Hi @tsvetanm,

Thank you so much for the follow up. We concur with your developers’ assessment and advice.

Meanwhile, we have reported this condition to the developer of Query Monitor for further evaluation and feedback.

Thank you.

@tsvetanm This is not correct at all. Query Monitor does not depend on heartbeat, it’s reporting that the heartbeat script is a broken dependency, presumably because it’s been deregistered and/or dequeued but the wp-auth-check script still depends on it. This is a broken dependency and this is what QM correctly reports.

This is the “canonical” original discussion on this topic, WP Engine used to do the same thing: https://www.ads-software.com/support/topic/suppress-presistent-errors-ex-broken-dependencies-wp-auth-check-on-wp-engine/.

Thanks, @johnbillion. I’ve reopened the topic. Great discussion.

Hi @generosus and @johnbillion,

Thank you for the report and information provided.

In the plugin we do recommend disabling heartbeat for admin pages as this will drastically reduce the account CPU usage and requests spawned by the website while admin pages are opened. This is explained in the description on the WordPress Heartbeat Optimization section:

The WordPress Heartbeat API checks your post edit pages every 15 seconds and your dashboard and front end every 60 seconds, even in the absence of scheduled tasks. This can generate high CPU usage if you leave browser tabs in which you’re logged to WordPress opened for a longer period of time. You can modify these settings to reduce load.

When the heartbeat is disabled for admin pages all scripts depending on it there will not be able to triger it in order to reduce the load.

Still it is up to the end user to deside wheather if the heartbeat will be disabled or it’s execution time frame will be changed.

Now about the suggested solution above. First of all, thanks to @generosus for the report and that a solution was suggested as well.

The solution applied in the the WP Rocket plugin – they are replacing the heartbeat script with an empty JS file. The depending scripts still can not use heartbeat functionality and simply the big red warning is being hidden by this.

It is normal that if I disable the WordPress Heartbeat for admin pages this will prevent some scripts of using it. That is why it is being disabled. And it is also normal that QM will report there is a dependency which is not available. So it is up to the user to decide wheather to leave it enabled or not.

Best Regards,
Elena

Hi @elenachavdarova,

Thank you for the update and detailed explanation. We agree with it.

Based on all inputs received, we can conclude that both plugins (QM and SGO) are performing as designed. The Javascript error noted in QM is simply a flag indicating that Heartbeat is disabled and certain WP functionalities may not work while Heartbeat is disabled.

For example, as noted by @johnbillion in this topic update:

wp-auth-check is a script that depends on heartbeat in order to function (it’s the script that ultimately shows a popup login window if your user session expires while you’re in the middle of doing something). Because heartbeat is missing, wp-auth-check won’t work.

Issue clarified and resolved ??

Thank you, y’all!