BitPay

Hi @disc4 – there have been a few enhancements to the plugin’s logging, and its logs now show in the WooCommerce interface:

1. Log into the WP admin
2. In the left nav, go to WooCommerce > Status
3. Click the Logs tab
4. You should see a bitpay_transactions source
5. Clicking on bitpay_transactions will take you into the logs

The order status being updated depends on BitPay’s webhooks being able to reach your site. When an invoice is created, the notificationURL property is set, and its value is $this->wordpress_helper->get_home_url() . '/wp-json/bitpay/ipn/status', with wordpress_helper being the BitPayWordpressHelper class.

After a payment flows through the network of the corresponding cryptocurrency, a webhook notification should be sent to that endpoint on your site.

This is where we can see some issues. One thing that would be great to confirm is if you have a CDN and/or WAF in front of your site, such as Cloudflare, CloudFront, Imperva, etc. If you’re not seeing webhooks sent to your site, it’s possible they’re being blocked.

Can you confirm if you or your host have a WAF in place, and if so, could you check the logs there to see if webhooks are being blocked?

Hi @disc4, this was released in version 6.1.2, and there’s a minor change to define the constant BITPAY_CHECKOUT_FOR_WC_PLUGIN_FILE early on in the lifecycle of the plugin, which uses __FILE__ in index.php. This helps some instances where the status was not being updated.

Have you tested this version?

Please note that we did just release version 7.0.0, however there are no significant changes other than dropping support for WooCommerce 9.7, following WooCommerce’s support policy.

Thanks @disc4 ! I’ve created an issue on our GitHub support issue tracker for us to look at, and will keep you posted.

Hello! Version 5.5.1 has been released with the change. Let us know if you continue to run into any issues and we’ll take a look. Thanks!

Thank you so much for the contribution @shaunek! We’ll take a look and give this a test tomorrow and plan for a patch release this week.

Thank you so much, @josn. Looking at this list, we see that you’re running version 4.1.0 of the BitPay Checkout for WooCommerce plugin.

Our first recommendation is that you upgrade the plugin to the latest version, 5.3.0 as the version you’re on is from July 2023 and is a legacy version. As of 5.0.0 it has been rewritten with various fixes and improvements.

Regarding PHP extensions, some are installed by default, but it’s worth checking your server configuration. You can find the installed PHP extensions by using the PHP (or PHP-FPM) CLI with the -m flag. You will need the following:

• bcmath or gmp
• curl
• iconv
• json
• openssl
• reflection

Please note that these are in addition to the PHP extensions required by WordPress.

If the above doesn’t work, the next step would be to use a local or test environment to disable all plugins except WooCommerce and BitPay Checkout for WooCommerce, as well as any third-party themes. Then, test with just the bare minimum. If that’s successful, you can re-enable plugins one at a time, testing after each. This will help us understand if one of the other plugins you have installed may be interacting with the BitPay plugin.

We look forward to hearing if this is helpful.

Thanks again!

• This reply was modified 2 years, 6 months ago by BitPay.

Hi @grindstonedsn , I wanted to let you know that we’ve released a new version of the plugin (5.3.0) which addresses warning #1. We are still awaiting further information on warning #2, which we are not able to reproduce. Please let us know if you are all set, and if not then we may be able to help if you can provide the requested information.

Hi @grindstonedsn I can see that these are not errors, but are warnings. I do have a few notes for you:

1. We recommend updating your PHP setup to not display warnings or errors, as a best practice because you don’t want to expose your server paths, libraries, and other information that tells the public about your setup.
2. Warning #1 (Trying to access array offset on value of type bool): This is a known issue that’s addressed in an upcoming release. This warning does not affect functionality.
3. Warning #2: Cannot modify header information – headers already sent: We will need to know more information about your specific setup, such as operating system, PHP version, web server configuration (Apache / nginx config), etc.

Please feel free to reach out with any other questions or additional information.

Thanks!