Fixora Heartbeat Manager

开发者	0322lf
更新时间	2026年9月29日 12:30
PHP版本:	7.4 及以上
WordPress版本:	7.1
版权:	GPLv2 or later
版权网址:	版权信息

下载

1.0.1

详情介绍:

Fixora Heartbeat Manager is lightweight heartbeat control for WordPress: allow, limit, or disable Heartbeat where it hurts performance, so admin-ajax polling does not burn CPU on shared hosting. WordPress Heartbeat (Heartbeat API) powers autosave, post locking, and other logged-in real-time features. Out of the box it can fire about every 15 seconds on edit screens and every 60 seconds on the dashboard. Many open wp-admin tabs → more admin-ajax.php?action=heartbeat traffic → higher CPU. Use Fixora Heartbeat Manager when you need to:

Control Heartbeat separately on dashboard, post editor, and frontend (logged-in)
Limit Heartbeat interval (15–300 seconds) to cut admin-ajax load and reduce CPU usage
Disable Heartbeat on the frontend or dashboard when you do not need it
Keep the post editor on Allow by default so autosave and post locks keep working

Safe defaults: dashboard limited to 60s, editor Allow, frontend disabled. Built for the same problem people search as heartbeat control / disable heartbeat / reduce admin-ajax CPU — with modern WordPress/PHP support and no heavy framework.

安装:

Upload the fixora-heartbeat-manager folder to /wp-content/plugins/, or install the ZIP from Plugins → Add New → Upload Plugin.
Activate Fixora Heartbeat Manager from the Plugins screen.
Go to Settings → Fixora Heartbeat and choose Allow / Limit / Disable per location.

屏幕截图:

升级注意事项:

1.0.1 Renamed to Fixora Heartbeat Manager with unique prefixes and uninstall cleanup.

常见问题:

What is the WordPress Heartbeat API?

It is a browser ↔ server polling mechanism via admin-ajax.php used while you are logged in (autosave, post locks, and related admin features).

How do I disable Heartbeat safely?

Disable on the frontend and/or dashboard if you do not need live admin polling there. Prefer Allow or Limit on the post editor — disabling Heartbeat in the editor can stop autosave and post locking. Fixora Heartbeat Manager defaults the editor to Allow.

Will this reduce admin-ajax CPU usage?

Yes, when you limit or disable Heartbeat in locations that were polling often. Fewer Heartbeat ticks means fewer admin-ajax.php?action=heartbeat requests.

Will this conflict with caching or performance plugins?

Fixora Heartbeat Manager only adjusts Heartbeat behavior. It does not replace a full page cache. You can use it alongside common performance plugins.

Is this affiliated with other Heartbeat plugins?

No. Fixora Heartbeat Manager is an independent plugin by Fixora Labs. It is not affiliated with WP Media, WP Rocket, or the Heartbeat Control plugin.

What data is removed on uninstall?

Deleting the plugin from the Plugins screen removes its single option (fxhbm_settings).

更新日志: