uzmak777

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

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

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 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

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

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