Source evidence

CLI support broken?

Dynamic Front-End Heartbeat Control · support · 2025-08-20T15:40:00+00:00

Dynamic Front-End Heartbeat Control plugin evidence original source source API

mixedsentiment

mediumseverity

0.5relevance

2replies

Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

6 / 35 rows with source links

17.1% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

29 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support

harryfear resolved

PHP Warning: require_once(/var/www/html/public_html/wp-content/plugins/dynamic-front-end-heartbeat-control/defibrillator/defibrillator/cli-helper.php): Failed to open stream: No such file or directory in /var/www/html/public_html/wp-content/plugins/dynamic-front-end-heartbeat-control/defibrillator/unclogger.php on line 15 Warning: require_once(/var/www/html/public_html/wp-content/plugins/dynamic-front-end-heartbeat-control/defibrillator/defibrillator/cli-helper.php): Failed to open stream: No such file or directory in /var/www/html/public_html/wp-content/plugins/dynamic-front-end-heartbeat-control/defibrillator/unclogger.php on line 15 PHP Fatal error: Uncaught Error: Failed opening required '/var/www/html/public_html/wp-content/plugins/dynamic-front-end-heartbeat-control/defibrillator/defibrillator/cli-helper.php' (include_path='.:/usr/local/lib/php') in /var/www/html/public_html/wp-content/plugins/dynamic-front-end-heartbeat-control/defibrillator/unclogger.php:15 Looks like there is a broken WordPress CLI handler there in Version: 1.2.9. Hi there @harryfear , Thank you for bringing this up. The error you experienced happened because the plugin was trying to load cli-helper.php from the wrong location. In some cases this can occur depending on how the plugin was installed or unzipped, which may slightly change the folder structure. I’ve updated the plugin so that it now automatically detects the correct path, regardless of how it’s installed. To fix this on your site, please remove the current version and install a fresh copy of the plugin from the WordPress repository . After that, the issue won’t appear again. If you have any other questions, feel free to reach out anytime. Kind regards, Amazing—thank you!

Commercial Context

Opportunity

performance monitoring and client reporting

Performance speed regression monitoring for keeping sites fast and proving optimization work

Buyer: site owners, agencies, and maintenance teams

Wedge: detect performance slowdowns, cache conflicts, asset regressions, and client-report impact

Proof Blocked card complete market

Analysis

codex:gpt-5.5

Summary: A bad bundled file path broke the plugin's WP-CLI handler until the vendor released a corrected install path.

Evidence quote: PHP Fatal error: Uncaught Error: Failed opening required

Affected feature: WP-CLI handler

bugs setup support WP-CLI handler

Plugin

API

Dynamic Front-End Heartbeat Control

1.0K active installs · 13.6K downloads · rating 96.0

admin-ajax heartbeat heartbeat api performance site health

Comments

2 shown

codeloghin 2025-08-21T00:27:00+00:00

Hi there @harryfear , Thank you for bringing this up. The error you experienced happened because the plugin was trying to load cli-helper.php from the wrong location. In some cases this can occur depending on how the plugin was installed or unzipped, which may slightly change the folder structure. I’ve updated the plugin so that it now automatically detects the correct path, regardless of how it’s installed. To fix this on your site, please remove the current version and install a fresh copy of the plugin from the WordPress repository . After that, the issue won’t appear again. If you have any other questions, feel free to reach out anytime. Kind regards,

harryfear 2025-08-21T10:55:00+00:00

Amazing—thank you!