Back to Community
Home / Community / Plugin → Disable gutenberg

Resolving Heartbeat API Interval Conflicts with Disable Gutenberg

12 threads Sep 9, 2025 Plugin → Disable gutenberg

Content

Users of the Disable Gutenberg plugin occasionally report an issue where they are unable to modify the intervals for the WordPress Heartbeat API. This can be a critical problem for site administrators looking to optimize their server's performance by reducing the frequency of the Heartbeat API's calls.

Understanding the Problem

The Heartbeat API is a WordPress system that uses AJAX calls to facilitate automatic saving and post locking. Some users, particularly those managing many sites, seek to control its interval to reduce server load. According to user reports, when the Disable Gutenberg plugin is active, other methods of controlling the Heartbeat API—such as adding custom code to the theme's `functions.php` file, using caching plugins like LiteSpeed Cache, or installing dedicated Heartbeat control plugins—may fail to work.

Why This Happens

While the sample support thread does not provide a definitive technical reason from the Disable Gutenberg team, plugin conflicts are a common cause in WordPress. The Disable Gutenberg plugin performs extensive modifications to remove the Block Editor and its associated scripts. It is possible that its operation interferes with the hooks or functions that other plugins or code snippets use to modify the Heartbeat API's behavior.

Common Solutions and Troubleshooting Steps

If you are experiencing this conflict, here are the most effective steps to troubleshoot and resolve it.

1. Verify the Conflict

The first step is to confirm that Disable Gutenberg is the source of the conflict. To do this:

  1. Deactivate the Disable Gutenberg plugin temporarily.
  2. Check if your Heartbeat interval modification method (e.g., code snippet, other plugin) now works as expected.
  3. If it does, reactivate Disable Gutenberg to see if the problem returns. This confirms the conflict.

2. Adjust the Loading Priority of Your Custom Code

If you are using a code snippet in your `functions.php` file, the order in which functions are executed can be vital. Try adjusting the priority of your hook to ensure it runs after Disable Gutenberg has initialized. For example:

add_filter( 'heartbeat_settings', 'my_custom_heartbeat_settings', 100, 1 ); // Note the high priority of 100
function my_custom_heartbeat_settings( $settings ) {
    $settings['interval'] = 120; // Change interval to 120 seconds
    return $settings;
}

3. Investigate Alternative Plugins

Since the conflict may be deep-seated, consider if an alternative plugin can achieve both your goals: disabling Gutenberg and controlling the Heartbeat. You may need to use separate, highly specialized plugins that are known to be compatible with each other.

4. Seek Support from All Involved Parties

As a neutral resource, BugWP.com recommends seeking information from the support channels for all plugins involved. The Disable Gutenberg team may have specific insights into known conflicts, and the developers of your Heartbeat control method may have encountered this issue before and have a workaround.

Remember, when a plugin is deactivated and uninstalled through the WordPress admin plugins screen, the Disable Gutenberg team has confirmed it automatically removes its only database option (`disable_gutenberg_options`), so testing by deactivating it is a clean and safe process.

Related Support Threads Support