=== Fixora Heartbeat Manager ===
Contributors: 0322lf
Tags: heartbeat, heartbeat control, admin-ajax, performance, optimize
Requires at least: 6.4
Tested up to: 7.1
Requires PHP: 7.4
Stable tag: 1.0.1
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Manage WordPress Heartbeat frequency in admin, editor, and frontend to reduce admin-ajax CPU load.

== Description ==

**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.

== Installation ==

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

== Frequently Asked Questions ==

= 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`).

== Screenshots ==

1. Settings overview with per-location controls
2. Limit interval options
3. Safety notice for the post editor
4. Lightweight settings screen in wp-admin

== Changelog ==

= 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.

== Upgrade Notice ==

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