WPIntell

Source evidence

Call Now Button Version 2 has issues

Call Now Button – The #1 Click to Call Button for WordPress · support · 2026-02-06T16:55:00+00:00

complaintsentiment
highseverity
0.38relevance
2replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

3 / 28 rows with source links

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

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

25 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
fzoid resolved
The new version that was just released today has issues. My sites contact paged crashed when clicked on from a mobile device. I sent you a support note on your website with more details. WordPress sent me a detail email and I sent you a copy of it. Hi there, Thanks for your message and for sending the details through via email. We investigated the issue and believe the error is internal to WooCommerce. A WooCommerce trait failed to load from within WooCommerce’s own code. Our plugin doesn’t interact with or modify WooCommerce’s class loading. This is the information about the error that’s in the email: An error of type E_ERROR was caused in line 27 of the file /xxx/xxxx/public_html/wp-content/plugins/woocommerce/includes/rest-api/Controllers/Version2/class-wc-rest-products-v2-controller.php. Error message: Trait "Automattic\WooCommerce\Internal\Traits\RestApiCache" not found In the email you received from WordPress it mentions the URL where the error occurred. This URL gives the impression that both plugins might have been updating at the same time, which caused the error. This url specifically would suggest this: update.php?action=update-selected&plugins=call-now-button%2Fcall-now-button.php%2Cwoocommerce%2Fwoocommerce.php It is likely that this corrupted the WooCommerce install. To resolve this, we would suggest the following: Use the recovery mode link in your email to access your dashboard Delete the WooCommerce plugin folder via FTP and reinstall it fresh In the future, update plugins one at a time rather than in bulk to avoid this type of conflict Hopefully this helps you get back up and running quickly! Kind regards, Jerry This reply was modified 3 months, 3 weeks ago by Jerry Rietveld . Reason: grammar typo Since there hasn’t been a response for a while, I’m going to mark this thread as resolved. If you’re still experiencing the issue, feel free to reply and I’ll be happy to help.

Comments

2 shown
Jerry Rietveld 2026-02-06T18:50:00+00:00

Hi there, Thanks for your message and for sending the details through via email. We investigated the issue and believe the error is internal to WooCommerce. A WooCommerce trait failed to load from within WooCommerce’s own code. Our plugin doesn’t interact with or modify WooCommerce’s class loading. This is the information about the error that’s in the email: An error of type E_ERROR was caused in line 27 of the file /xxx/xxxx/public_html/wp-content/plugins/woocommerce/includes/rest-api/Controllers/Version2/class-wc-rest-products-v2-controller.php. Error message: Trait "Automattic\WooCommerce\Internal\Traits\RestApiCache" not found In the email you received from WordPress it mentions the URL where the error occurred. This URL gives the impression that both plugins might have been updating at the same time, which caused the error. This url specifically would suggest this: update.php?action=update-selected&plugins=call-now-button%2Fcall-now-button.php%2Cwoocommerce%2Fwoocommerce.php It is likely that this corrupted the WooCommerce install. To resolve this, we would suggest the following: Use the recovery mode link in your email to access your dashboard Delete the WooCommerce plugin folder via FTP and reinstall it fresh In the future, update plugins one at a time rather than in bulk to avoid this type of conflict Hopefully this helps you get back up and running quickly! Kind regards, Jerry This reply was modified 3 months, 3 weeks ago by Jerry Rietveld . Reason: grammar typo

Jerry Rietveld 2026-02-09T12:07:00+00:00

Since there hasn’t been a response for a while, I’m going to mark this thread as resolved. If you’re still experiencing the issue, feel free to reply and I’ll be happy to help.