[wp-trac] [WordPress Trac] #41903: Unable to deactivate Heartbeat API

[WordPress Trac]

#41903: Unable to deactivate Heartbeat API
----------------------------+------------------------------------------
 Reporter:  markbowenpiano  |       Owner:
     Type:  defect (bug)    |      Status:  closed
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  General         |     Version:  4.8.1
 Severity:  normal          |  Resolution:  invalid
 Keywords:  close           |     Focuses:  administration, performance
----------------------------+------------------------------------------

Comment (by JPry):

 Replying to [comment:3 markbowenpiano]:
 > Sorry for that. I had thought (obviously wrongly) that this was for
 WordPress bugs. Very new to WordPress so may have misread that when
 posting the ticket.

 This is indeed for WordPress bugs, but in this particular case the bug is
 with either your site or your code rather than with WordPress itself.
 Using the steps that you described, I was able to deregister the Heartbeat
 API.

 > If I could possibly quickly ask if it is even possible to turn off the
 Heartbeat and if it is then I can ask elsewhere or even hire a developer
 to see why it won't turn off.

 It is possible to turn off the Heartbeat API, but it is there for a
 reason. Determining whether a post is already being edited is one of its
 uses but it is not the ''only'' use.

 Your code ''appears'' to be correct, so I can't say why it's not being
 disabled. It may be a good idea to look for a plugin that can help you
 control the Heartbeat API with more detail.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/41903#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform