@heathcliffe2000 — @bacchusfugue — yes, we removed that option here [1] as we realized that it was causing more issues than not. This was not a security related feature, the purpose for this option was to allow web masters to disable the heartbeat functionality if — and only if — they were experiencing issues with the latency of the API service, since the heartbeat generates a significant amount of HTTP requests. After the rest of the code was improved, we decided that the option was not necessary anymore.
We have no intention to re-implement this option again, I believe another developer can copy and paste the code from the commit linked below and offer this functionality with a different plugin.
[1] https://github.com/sucuri/sucuri-wordpress-plugin/commit/f45dd8e
Thread Starter
Cliff
(@heathcliffe2000)
@yorman, many thanks for the reply. My specific query was with regard to the settings.
Are the setting RESET back to default as a result of upgrading?
@heathcliffe2000 — yes, the settings were automatically reset back to their default values. The plugin was using “add_filter” [1][2] to modify the settings for the heartbeat API at runtime, deleting the code caused these settings to be back to its normal state. However, if you notice anything strange after the upgrade of the plugin please let me know and I will investigate.
[1] https://github.com/sucuri/sucuri-wordpress-plugin/commit/f45dd8e#diff-198096ad83dfc8152a10d95eb1b6b598
[2] https://developer.wordpress.org/reference/functions/add_filter/
