jsk
Forum Replies Created
-
Thank you. The issue does not appear to be present in version 4.7.9 so I believe the problem is resolved.
Thank you for the feedback. Firstly, we have not used any custom code snippet to add the SKU column but have been using it as is out of the box and have always had the SKU column and with all the characters, in the format #####-## or #####-###.
I downloaded and downgraded the plugin to a previous version but the issue persisted so I re-installed the latest version. The problem did not go away. However, strangely enough, I deactivated and then re-activated the plugin and the problem went away so it is working now as it was previously!
I have used the link you provided to provide the status report (page does not acknowledge the submission so not sure if it went through or not).Forum: Reviews
In reply to: [WooCommerce Shipping] This is not an upgrade but a downgradeUpdated to version 1.1.5. Tried to “Edit Origin Address”. When I click “Validate”, I get the error, “Error: The WooCommerce Shipping server returned: Bad Request child “destination” fails because [“last_name” is not allowed] ( 400 )”.
Please advise how one can edit origin address during shipping label creation.PS: Same error was happening on Version 1.1.3.
In the meantime, how can I get the previous version that worked very well to use while these issues are addressed?Forum: Plugins
In reply to: [WooCommerce] Invalid or missing payment@rajeshml the issue has been resolved. It was caused by a Siteground optimizer plugin, specifically the setting “Combine Javascript Files”. Disabling that feature resolved the issue.
Forum: Plugins
In reply to: [WooCommerce] Invalid or missing paymentThis is what is happening over the last few days…
With Woopayments enabled, at the checkout page, the option for a customer to enter card details does not become visible so there no option to enter credit/debit card details. When one clicks the “Place Order” button, one gets the error, “Invalid or missing payment details. Please ensure the provided payment method is correctly entered.”. At that point, the card number, expiration date and security code text boxes become visible/enabled. The customer order comes through as “Failed” with no details as to why it failed.This appears to be a defect/bug in the current version. Currently running Woopayments Version 8.2.1.
Having same issue where orders come in without the customer details. Sometimes, order would be processed twice, one with the details and the other without. In one instance, customer was charged twice.