David Skyverge

Hey there,

It has been a long time since we heard from you, so I’m going to mark this topic as resolved.

If you’re still experiencing issues please take a look at our FAQs for more information and create a new thread if you have further questions.

Thanks,
David

Hi @gtaheatca!

David here, stepping in, and?I’m sorry to hear that you are still having issues with this on your WooCommerce store. I’m happy to help! ??

I want to thank you for providing a link to your debug.log file. This is truly helpful!

I was able to locate the following message:
[02-Oct-2024 13:08:49 UTC] PHP Warning: openssl_sign(): supplied key param cannot be coerced into a private key in /home/u245370445/domains/hydronicsdepot.com/public_html/wp-content/plugins/godaddy-payments/vendor/firebase/php-jwt/src/JWT.php on line 242

I have taken a look at this, and found that it may be an issue with the private key that you are using in your WooCommerce settings for GoDaddy Payments. This can break if a site migrates servers or a domain is changed.

To see if this is the case, you can perform the following steps to reset it.

1. Log in to your GoDaddy Payments dashboard and go to Business Settings > Contact Info.
2. Copy your Application ID and Private Key in the Poynt Collect API Settings section. (Re)generate the Private Key.
3. In your WooCommerce store, go to WooCommerce > Settings > Payments > GoDaddy Payments and (re)paste these credentials in the Application ID and Private Key fields.
4. Click Save Changes.

Can you give this a try and let me know if it works?

Thanks,
David

Hi @riseofweb,

Thank you for reaching out about our plugin, GoDaddy Payments for WooCommerce! I’m sorry for the delay in responding to you here. I’m happy to assist you with this. ??

Thanks for providing me with a copy of the messages that are showing up in your logs. This is truly helpful.

I have tested GoDaddy Payments on a cPanel account and was unable to recreate the messages you are sharing with just WooCommerce and GoDaddy Payments enabled. I have seen a similar issue with Jetpack enabled recently, so I tested with this plugin and was able to recreate this message that way.

This is suggesting that there may be a conflict happening with GoDaddy Payments and the Jetpack plugin. Can you tell me if you are using Jetpack on your site? If so, can you also tell me if the message stops being created when it is disabled?

Thanks!
David

Hey there,

It has been a long time since we heard from you, so I’m going to mark this topic as resolved.

If you’re still experiencing issues please take a look at our FAQs for more information and create a new thread if you have further questions.

Thanks,
David ??

Hi @seanconklin,

Thank you for reaching out! I understand how important it is for your business to have the flexibility and control of your checkout pages.

Although I cannot give you a date for when the update will be released, I can tell you that we are actively working and testing the final touches to make GoDaddy Payments compatible with the new block editor.

Until the update is stable and ready for use, the WooCommerce shortcode [woocommerce_checkout] will continue to work.

I appreciate you voicing your concern and we hope to have this update available soon.

All the best,
David