Heartbeat interval problem
-
hello,
I am facing an issue related to the “Disable Gutenberg” plugin in my WordPress setup. The primary problem revolves around the inability to change the Heartbeat API intervals when the “Disable Gutenberg” plugin is activated. Despite trying various approaches, I have not been able to modify the Heartbeat API intervals effectively.
Here is a concise breakdown of the problem and the steps I’ve taken:
- Manual Code in functions.php: I attempted to manually change the Heartbeat API interval by adding custom code to the
functions.php
file of my theme. However, even with the code in place, the Heartbeat API intervals remained unchanged. - LiteSpeed Cache Integration: I explored using the LiteSpeed Cache plugin to manage Heartbeat API intervals. Despite configuring the LiteSpeed Cache settings to modify the intervals, the changes were still not reflected in the functionality. This suggests that the issue is not specific to the LiteSpeed Cache integration.
- Heartbeat Control Plugin: I also installed and tested the “Heartbeat Control” plugin, which is designed to provide control over the Heartbeat API intervals. However, even with this plugin active, I encountered the same problem: the Heartbeat API intervals did not change as intended.
What’s interesting is that when I completely disable the Heartbeat API, the plugin works as expected. However, I do not want to disable the Heartbeat API entirely, as it serves important functionality.
To gain more insight into the issue, I monitored the
admin-ajax
requests using the Chrome browser’s inspect network section. Despite observing these requests, I have not been able to pinpoint the exact cause of the problem.I’m seeking assistance to identify the root cause of this compatibility issue and find a solution that enables me to change the Heartbeat API intervals without having to disable it entirely.
- Manual Code in functions.php: I attempted to manually change the Heartbeat API interval by adding custom code to the
- The topic ‘Heartbeat interval problem’ is closed to new replies.