外掛說明
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-managerfolder 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.
常見問題集
-
What is the WordPress Heartbeat API?
-
It is a browser server polling mechanism via
admin-ajax.phpused 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=heartbeatrequests. -
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).
使用者評論
這個外掛目前沒有任何使用者評論。
參與者及開發者
變更記錄
1.0.1
- Renamed to Fixora Heartbeat Manager (slug
fixora-heartbeat-manager) following plugin review. - All functions, classes, constants, options, handles and settings identifiers now use the unique
fxhbm_/FXHBM_prefix. - Added uninstall cleanup.
1.0.0
- Initial release: Allow / Limit / Disable Heartbeat on dashboard, editor, and frontend.