PHP Fatal error

Hi Joe,

Thanks for your message. And double thanks for sharing the full error notices. We’re investigating the issue but it seems to be related to an incomplete update of the Call Now Button.

You should be able to fix this by uninstalling and re-installing the plugin. So via the WordPress Plugins page on your admin dashboard locate the Call Now Button > click Deactivate > click Delete and then reinstalling it by clicking Add new and then searching for Call Now Button > click Install > click Activate.

Hope this helps. If we find out more, we’ll let you know.

Cheers,
Jerry

Hi Joe,

Hope the reinstallation solved the issue for you. Since I haven’t heard from you anymore, I’m going to mark this issue as resolved. If it isn’t, let me know and we’ll reopen this again.

Cheers,
Jerry

Hi, reinstallation didn’t solve the problem
WP 6.0.1
PHP 7.4.5

Hi Joe,

Sorry to hear that the issue wasn’t resolved through a reinstall. We’ve been thoroughly investigating the issue you’re experiencing but have been unable to reproduce it. We can investigate further, but we would need more details about your specific setup. If you want us to do that, please submit your details via our support form here.

Best,
Jerry

Hi Joe,

Thanks for submitting your issue via our support form as well. I’ve already send you an email, but I’m adding the content of the email here as well in case others run into the same issue:

We’ve tried to reproduce the issue many times and were only successful?when we completely removed the file that’s referenced in the error?message. That would indicate that the file was corrupted?(damaged) during the installation process. A re-install should then have fixed the issue. It’s incredibly rare for a file to get corrupted during the download and installation process, so it is even more unlikely that it happens to you twice (I’m assuming that you fully deleted the plugin and did a full re-download and installation again, right?).

Unfortunately there’s?not much else we can do anymore. We’ve reviewed the code, the internal validations (does the file exist, does the function exist, etc.) and those are all in place and working properly. So if the reinstall doesn’t solve the issue, then there might be a process on your web server that’s causing?this. You could ask your web host to investigate the issue. They can see the structure of the folder,?manually extract the zip file and install the plugin to see what happens on their end during this?process.

I also get Fatel Error after last update.
It happens and night twice for the last 2 days and i fix it by deleting the plugin and reinstalling it.
It gives the following error:

2022/07/27 13:22:46 [error] PHP Warning:  require(/home/XXXXXX/domains/XXXXXX.com/public_html/wp-content/plugins/call-now-button/src/admin/apikey/CnbApiKeyController.php): failed to open stream: No such file or directory in /home/XXXXXX/domains/XXXXXX.com/public_html/wp-content/plugins/call-now-button/src/autoload.php on line 108
PHP Warning:  require(/home/XXXXXX/domains/XXXXXX.com/public_html/wp-content/plugins/call-now-button/src/admin/apikey/CnbApiKeyController.php): failed to open stream: No such file or directory in /home/XXXXXX/domains/XXXXXX.com/public_html/wp-content/plugins/call-now-button/src/autoload.php on line 108
PHP Fatal error:  require(): Failed opening required '/home/XXXXXX/domains/XXXXXX.com/public_html/wp-content/plugins/call-now-button/src/admin/apikey/CnbApiKeyController.php' (include_path='.:/usr/local/php73/lib/php') in /home/XXXXXX/domains/XXXXXX.com/public_html/wp-content/plugins/call-now-button/src/autoload.php on line 108
client: 82.166.199.1, server: XXXXXX.com, request: "GET /wp-admin/plugins.php?activate=true&plugin_status=all&paged=1&s= HTTP/2.0", upstream: "fastcgi://unix:/usr/local/php73/sockets/talisina.sock:", host: "www.XXXXXX.com", referrer: "https://www.XXXXXX.com/wp-admin/plugins.php"

please advise

Hi sinaydavid,

Thanks for your message and sorry to hear that you’re running into the same issue. Troubleshooting errors like this is incredibly hard with WordPress because plugins are installed locally and we can’t see what happens on the servers.

I would advice that you contact your webhost and have them look into this. The error message reports a missing file which would indicate that the installation is faulty.

Your web host can manually extract the zip file and see what is really happening. They can validate if the file CnbApiKeyController.php is actually where it should be (is the path correct: /home/XXXXXX/domains/XXXXXX.com/public_html/wp-content/plugins/call-now-button/src/admin/apikey/). If not, is the file placed in a different folder? Are there maybe error messages during the installation/extraction on the server?

I really wish I could help you, but the issue is occuring on your webserver and we have no visibility on this part.

If you reach out to your web host, it would be great if you could share their findings. Obviously we would really like to understand this as well. If you prefer not to share that publicly this forum, you can also do this via our support form.

Thanks and again sorry that we can’t be of more help with this…

Jerry

They said you guys need to sort it..

That sounds like a host with a great support team. I’ve explained to you why we can’t help you and why your webhost can. As much as I want to help you, I simply can’t.

Hi all! Just a quick update on this. In total 4 people have flagged this issue. 2 of those shared their website domains and both of them had their websites hosted with Upress. That’s a little too much coincidence…

We reached out to them for help, but they kept dismissing it as a plugin issue and not server related.

We then went ahead and set up a website ourselves on Upress. Everything was working well, but the next day we had a critical error and the site was put in recovery mode. We looked at the plugin files and noticed that the entire /apikey/ folder was removed from the plugin. We re-added the folder and the next day (today) the same thing happened again.

Upress seems to be doing a scan once a day and just deletes files and folders that match specific names. This is an incredibly aggressive approach and is guaranteed to have dramatic side effects (like breaking entire websites). This also confirms that it really is a server issue and has nothing to do with the plugin. It’s really a shame they weren’t more helpful trying to resolve this.

We’ll rename the folder in the plugin and release an update soon. That should solve the Upress issue for everyone. Fingers crossed we don’t pick another name from their list ??

Cheers,
Jerry