The settings refer to the time between heartbeat requests across any location, while the location dropdown is simply where the heartbeat will active/inactive.
For example, if you select 60s and “only on post edit pages”, the WordPress heartbeat will only be active on those pages, and will be slowed to one request per 60 seconds (on those post edit pages where it is still active).
Disabling on dashboard pages simply means that when you are within wp-admin, the WordPress heartbeat will be inactive. The “post edit pages” option means that it will only be active when editing a post or page.
Yes, the UI isn’t the greatest, simply because I don’t have a whole lot of time to devote to improving it. If you would like to help with the UI, I welcome pull requests on the GitHub repo:
https://github.com/JeffMatson/heartbeat-control
Jeff,
Thanks so much for your reply.
2) does DISABLE EVERYWHERE mean “no heartbeat”.
3) Which setting do I use if want 60s everywhere?
Cheers
Disable everywhere does indeed disable the heartbeat API completely (unless in rare cases another plugin is re-enabling it in which 99% of cases, is fine.)
If you want it to be 60 seconds everywhere, select 60 seconds from the timing dropdown and select “Use Default” in the location dropdown.
Most excellent.
I appreciate this plugin Jeff.
Great HeartBeat Graphic btw.
Thanks for clarifying these things! This thread is a very helpful addition. I know that you don’t have time, but am looking forward to the day when these explanations are at least included in the plugin homepage description or FAQs, and ultimately on the plugin settings page.
I hate to be a stickler but you wrote:
The “post edit pages” option means that it will only be active when editing a post or page.
So, does not apply to Custom Post Types then, is that right?
Also, you wrote:
if you select 60s … the WordPress heartbeat will … be slowed to one request per 60 seconds
What is the WordPress “default” setting: every 15s?
Thanks again!
