WordPress - Heartbeat

Opening the File Manager and Locating the Target File   

1. Log in to cPanel. There are two ways to access your cPanel.
   • Option 1: Access your cPanel directly.
   • Option 2: Access your cPanel via your Customer Portal.
     1. Log in to your Customer Portal.
     2. Click Hosting in the left-side menu.

        

     3. If you have a single hosting package in your account, scroll down to the Quick Links section.

        
        If you have multiple hosting packages in your account, locate the hosting package you want to manage on the Hosting Packages page, then click its Manage button.

        

     4. Under the Quick Links section, click the cPanel button.

        

2. In the Files section, click on the File Manager icon.

   

3. Locate the Document Root and select the domain name you wish to access from the dropdown menu.   
4. Find and double-click your target folder icon. (You may also navigate to the target folder using the directory tree of folders in the left sidebar.)  
5. In the folder, locate the target file. You may need to scroll to find it.

Editing a File    

1. Right-click on the file you wish to edit. Click Edit from the menu.
2. A dialogue box may appear asking you about encoding. Just click Edit to continue. The editor will open in a new tab.    
3. Edit the file as suggested.    
4. Click Save Changes in the upper right-hand corner when done. The changes will be saved.    
5. Test your website to make sure your changes were successfully saved. If not, correct the error or revert to the previous version until your site works again.  
6. Once complete, you can click Close to close the File Manager window.

When trying to save on CPU resources, it may be worth considering the benefits of the features provided and determining if you need this API active at all. For sites with multiple editors working on posts together, it may not be essential to have post locking enabled. If your posts are typically short and easily reproduced, it may not be worth consuming resources to enable autosaving.

Towards the top of the functions.php file, add the following code to disable the Heartbeat API everywhere:

add_action( 'init', 'stop_heartbeat', 1 ); function stop_heartbeat() { wp_deregister_script('heartbeat'); } 

The Heartbeat API enables users to customize every moment of a visitor's experience on their site. This includes the ability to use behind the scene server tasks to disable or enable a notice on the screen anytime a value in the database changes. If you do not want to lose this functionality but still need to trim down the resources your script is using, add the code below to disable the API on your Dashboard only.

add_action( 'init', 'stop_heartbeat', 1 ); function stop_heartbeat() { global $pagenow; if ( $pagenow == 'index.php' ) wp_deregister_script('heartbeat'); } 

The Heartbeat API for WordPress can be disabled everywhere except for posts (post.php and post-new.php). Add the code provided below. This will allow the browser to send updates to the server when writing or to edit a post to maintain the autosave and post locking features.

add_action( 'init', 'stop_heartbeat', 1 ); function stop_heartbeat() { global $pagenow; if ( $pagenow != 'post.php' && $pagenow != 'post-new.php' ) wp_deregister_script('heartbeat'); } wp_deregister_script('heartbeat'); } 

If you would like to keep all the features of the Heartbeat API but are battling high CPU loads, you may consider changing the update rate. By default, updating happens every 15 seconds for pages that are focused and every 2 minutes for pages that are non-focused. (WordPress identifies a page as non-focused when there have been 5 minutes of inactivity within the browser.)

add_filter( 'heartbeat_send', 'my_heartbeat_settings' ); function my_heartbeat_settings( $response ) { if ( $_POST['interval'] != 60 ) { $response['heartbeat_interval'] = 60; } return $response; }