Hello,
Thank you for your question. Your issue seems to come from your web server configuration paths not being properly set up. Kindly check the plugin’s root directory, folder ‘defibrillator’ to confirm that the file ‘cli-helper.php’ exists and has the proper access permissions set by your web server. I recommend you look into the relative and absolute paths, in the file system and on the web server as it sounds like your issue comes from a misconfiguration there. This can impact functionality beyond just this plugin.
For any other questions feel free to reach out!
Kind regards,
Codeloghin
Hi @codeloghin ,
Thanks for your response.
Just to clarify, the issue doesn’t seem to come from our server configuration, but rather from a wrong file path within the plugin code.
Here’s the error log (server path trimmed for privacy):
PHP 10. require() /public_html/wp-content/plugins/dynamic-front-end-heartbeat-control/heartbeat-controller.php:450
PHP 11. require() /public_html/wp-content/plugins/dynamic-front-end-heartbeat-control/settings.php:35
PHP 12. DynamicHeartbeat\DfehcUnclogger->__construct() /public_html/wp-content/plugins/dynamic-front-end-heartbeat-control/defibrillator/unclogger.php:108
PHP Fatal error: Uncaught Error: Failed opening required '/public_html/wp-content/plugins/dynamic-front-end-heartbeat-control/defibrillator/defibrillator/cli-helper.php' (include_path='.:/usr/share/php') in /public_html/wp-content/plugins/dynamic-front-end-heartbeat-control/defibrillator/unclogger.php:15
However, the file cli-helper.php does exist in the following location:
/public_html/wp-content/plugins/dynamic-front-end-heartbeat-control/defibrillator/cli-helper.php
So it looks like the plugin is incorrectly referencing a double defibrillator/defibrillator/ path. Could you please confirm and fix the path in the plugin code?
Thanks again for your help!
Hello,
Thank you for your response. The plugin code is fine. If you think your file might be corrupted, it’s best you completly remove and reinstall the plugin. If you are still experiencing the same issue, I highly recommend double-checking the server environment settings.
Best regards,
Codeloghin