Mandatory fields are not being verified

Update: I just deactivated this plugin and then tried the basic fields in the Woocommerce checkout form and all of the required fields verification is working fine. I clicked the Place Order field and the error immediately raised mentioning the required fields.

So it is confirmed that this plugin caused the verification of required fields in the check out form broken and is causing the above problem.

Support team, could you please check this problem?

Thanks

Hey there,

My apologies that this is happening to you.

I understand that you have deactivated the GoDaddy Payment Gateway plugin, but are still receiving an error. I’d love to dive in to try and get this resolved for you!

What is the error that you are receiving?

Sometimes the payment gateway areas will spin when there is a missing setting under WooCommerce > Settings > Payments > GoDaddy Payments (Manage). Could you verify that the settings in this area are fully setup?

Cheers,

Amber

• This reply was modified 1 year, 12 months ago by amberskyverge.

Hi Amber,
I reactivated the plugin again. I deactivated just because of verification of Woocommerce default null fields check in case of a customer click the ‘Place Order’ button.

Actually, there is no error appearing. Let me explain again what is going on. Just think of a website when you enter an item into a cart and then proceed to the check out process. Once you are at the screen where you are supposed to enter the name, address, credit card number, expiration date and CVV fields, click the ‘Place Order’ button leaving Credit Card, expiration and CVV fields without any values in them.

In reality, you should expect an alert if you keep any of these three fields as null and tries to click the ‘Place Order’ button because it shouldn’t be a complete order with out having Credit card number, expiration date or CVV fields empty. In my case, if I keep these fields empty and click the ‘Place Order’ button, it hangs the screen and shows the spinning circle instead of raising an alert for customers to fill out these fields.

Hope this will be clear enough to give you an idea about what I am talking about. You can try to simulate this in your testing environment. Just click the Place Order button keeping these fields empty and see what happens.

Thanks

Hey @uzmak777,

Thanks for the details on this, very helpful!

I tested this on my test site with just GoDaddy Payments and WooCommerce active. On Checkout, I left all credit card fields empty and received the message “Missing card details.” at the top of the Checkout page. I tested with just some of the fields filled out and had the same result, which is what should be happening on your site.

It might be that a conflict is responsible for this issue, so I’d like to try to rule out a theme conflict first.

Would you please temporarily switch to a default theme, such as Twenty Nineteen, and let me know if the issue persists? If it does persist, not to worry, I’ll have some other troubleshooting steps for you to follow.

If swapping themes does resolve the issue, it would appear to be a theme conflict.

Would you please let me know how the theme switch went?

Cheers,`

Steve

Hi Steve,
I only have production website and don’t have any staging environment where I can try switching with any other theme. I am little nervous in making any change like changing theme which may override my current website settings.

I currently have Astra’s Fashion Designer Free theme. Is it possible for your team to install this theme on your sandbox server and test the plugin like you did for the default theme? It would then confirm whether this theme is culprit or this plug in?

I appreciate for your help.

Thanks

Hey @uzmak777,

I installed Astra’s Fashion Designer Free theme on my test site and attempted to complete the order without any information in the credit card fields. I received the “Missing card details.” message with the theme in its default settings and a standard WooCommerce Checkout page:

https://cloud.skyver.ge/Jruyv9XW

Is your Checkout page using the shortocode, or is it designed with a page builder, such as Elementor?

If you are using a page builder for checkout, can you please test this with a standard WooCommerce checkout page, using the [woocommerce_checkout] shortcode, and let me know if this helps?

Cheers,
Steve

I did enable the logging in the Woocommerce and fount out the following fatal error:

2022-11-21T04:13:09+00:00 CRITICAL Uncaught DomainException: OpenSSL unable to sign data in /home//domains//public_html/wp-content/plugins/godaddy-payments/vendor/firebase/php-jwt/src/JWT.php:211
Stack trace:
#0 /home//domains//public_html/wp-content/plugins/godaddy-payments/vendor/firebase/php-jwt/src/JWT.php(180): Firebase\JWT\JWT::sign('eyJ0eXAiOiJKV1Q...', '-----BEGIN RSA ...', 'RS256')
#1 /home//domains//public_html/wp-content/plugins/godaddy-payments/src/API/Requests/GenerateTokenRequest.php(77): Firebase\JWT\JWT::encode(Array, '-----BEGIN RSA ...', 'RS256')
#2 /home//domains//public_html/wp-content/plugins/godaddy-payments/src/API/Requests/GenerateTokenRequest.php(48): GoDaddy\WooCommerce\Poynt\API\Requests\GenerateTokenRequest->generateJwt('urn:aid:92f3dd8...', '-----BEGIN RSA ...', 'https://service...')
#3 /home//domains//public_html/wp-content/plugins/godaddy-payments/src/API/ in /home/u241967494/domains/mkfashionsclothing.com/public_html/wp-content/plugins/godaddy-payments/vendor/firebase/php-jwt/src/JWT.php on line 211

I’ve deleted my domain information from the above lines. Do you know about the above error? Is the generated token not correct (even though I’ve generated twice)?

Thanks

Hi @uzmak777
?
Thank you so much for your patience.
?
?I’ve reviewed the PHP error you provided us. Thanks for giving us that.
?
I think the SSL warrants checking, based on the error. ?I would like to ask if the site SSL is working as expected. When you visit the site, do you see the secure lock icon?
?
?Thank you!

Yup, my website is showing the lock sign. When I click on the lock it shows a message that ‘You are securely connected to this site’. SSL certificate is issued by Hostinger provider. I also contacted them and they mentioned me that this error was originating from the app itself.

Hope this helps.

Thanks

Hey @uzmak777 ,

I did some further testing on a different clean test site and reproduced the issue you are seeing.

I’ve added this to our issue tracker for the developers to get this patched up. While I don’t have an estimated time for resolution right now, please know that our team is aware of the issue and will work to incorporate a fix into the plugin as soon as possible.

Thanks so much for reporting this! Is there anything else I can help out with?

Cheers,
Steve

Glad that you were able to produce this error and hoping to get the resolution soon! Thank you Steve.

Hey @uzmak777 ,

Thank you for making us aware of this bug! I’m going to mark this topic as resolved, but if you have any other questions or issues, please take a look at our FAQs for more information and create a new thread if you have further questions.

Best,
Zach