BitPay

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!

Hey @shaunek — this is exactly the kind of engagement we’re hoping for from the community and are surely open to features and functionality. It would be fantastic if you could open an issue to give us a heads up, and then I’ll run through it with everyone. There we can discuss how we want to approach it. For example, something like this might be a great fit for a setting. 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.

Thanks for reaching out @rbrynest – could you also share the following?

• Which version of WooCommerce you’re running
• Which PHP extensions are installed
• All other plugins and their versions

Finally, did you enable the method prior to clicking Finish set up?

Thanks again!

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 1 year ago by BitPay.

Hi there! Could you share your version of PHP, list of PHP extensions, version of WordPress, and WordPress plugins (with versions)? That will help us check this out for you.

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 @zaka888 ! I hope you found what you needed by reaching out to BitPay support regarding your BitPay account, but I wanted to let you know that the new version of the plugin has been released (5.3.0), which has the option to select your button.

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!

Hi @ellisrl we’re looking into this, as it’s a result of a sub-dependency update. There was an issue with another plugin using a very outdated version of Guzzle, which caused issues. The solution to that was to introduce php-scoper (similar to Yoast) to prefix all vendor packages with a custom namespace.

We’ll check this out on our end. In the mean time, you should be OK to use the previous version prior to the introduction of php-scoper.

Please note that we are only supporting PHP 8.0 until November 26th, 2023 when it will reach the end of its security updates.

@zaka888 since account is a sensitive issue that can’t be resolved on the forums, it would be great if you could reach out through https://bitpay.com/request-help/wizard and we can get you some clarification regarding acceptance. There’s a chatbot to get started and will help direct you to someone in support if you can’t find what you’re looking for.

Hi there @zaka888 we just wanted to give you a quick heads up that we’re working on releasing version 5.1.0, and in parallel are working on 5.2.0 that will have this button selection feature.

Alrighty @zaka888 , I’ve talked to my teammates that handle this part of onboarding and they said that while we prefer the version that the plugin currently comes with, you can use other marks from the guidelines.

I believe this will give you two paths forward:

Near-Term

You could modify the plugin directly. This is not recommended and changes would be wiped on a plugin upgrade but that’s up to you and your development workflow.

Long-Term

We are putting a story on our backlog for review and will link it to a GitHub issue. This story will add a dropdown to the configuration to allow you to choose from the various buttons.

Thanks again for reaching out, this is a real-world feature that we’ll add to the plugin!

Got it, thank you so much for the clarification – I’m checking on this for you and will report back.

Hello,

We have guidelines for how the payment mark should be used in the link that was provided in our previous post (https://developer.bitpay.com/docs/checkout-page).

A screenshot would be very helpful, however without that available I believe you’re referencing the payment mark that is used, which is https://bitpay.com/cdn/merchant-resources/pay-with-bitpay-card-group.svg, which is the intended image.

NOTE: I do see that on the plugin page in the WP marketplace that the third screenshot shows an option to change the button, but it appears that this may be a cached file on the WP marketplace CDN and is not showing the latest screenshots as this option was removed for branding purposes.

If you are having a specific issue or the plugin is not working as intended, please provide as much information as possible. Examples include:

• Your operating system
• PHP version (I understand you’re on version 8.0.30)
• WordPress version
• WooCommerce version
• All other plugins and their versions

If the primary issue is that you are not happy with the default logo, you should be able to override the bitpay_logo CSS class, but I cannot guarantee that an image you choose would be in-line with brand usage guidelines.

Finally, the plugin is open source, so if you’d like to contribute to the codebase, we welcome you to submit a pull request our GitHub repository.