RobertGomez

Wow, thanks for all the help! Awesome plugin and super support!
-Rob

I am having the same issue, have tried all the steps listed above with the same results. Any chance there will be an update soon?

@bheadrick or @joelwarren

Any chance you can look at this and fix an issue?

Example taken from a post by @mcnitefly”
When you have a product with two attributes: color and size and I use one GET parameter in the URL, “color”, the link that gets created is correct and points to the product variation of the correct color. But the other attribute – size in this example – needs to be selected, too and is not. (Gets set to “Choose an option”)

WooCommerce has the option to set default parameters for the attributes. Keeping these parameters would solve the issue – but the link that gets created by “WooCommerce Direct Variation Link” seems to overwrite these default parameters. Even the ones that where not addressed by the URL created.

• This reply was modified 7 years, 7 months ago by RobertGomez. Reason: added @joelwarren

@tychesoftwares

I will email you here in a min. Thanks for the help!

@tychesoftwares I am running Woocommerce Version 3.1.2 and when I was running WooCommerce Print Invoice & Delivery Note Version 4.1.5 I could see the Variations (size, color…) Now I can’t

Also with v4.1.5 and running the Fancy Product Designer it would show a bunch of metatdata (fpd_data) that was unneeded, I can give you access to 2 staging environments if you want to see both versions in action.

No, I see it in my authorize sandbox. I was hoping you could look into adding more detailed errors.

Ok, Thanks. For the detailed errors from authorize.net I am just seeing “This transaction has been declined.” not “The card verification number does not match.”

So are you saying that is all that can be done?

If that is the case can you make it show detailed decline messages? I want users to know why the card was declined.

Thanks!

Sorry for the late reply… While this update does add and remove the * from the field it does not make the field required, I can still submit an order with the field blank.

no worries, thanks for the help!

I disabled all my plugins except woocommerce ones, I still get the same error. Tested the version I have on my live site on the dev site and it works, so i put the new one from the code above and it fails so something seems to be failing on the updated version.

1-https://stage.decodip.com/shop/
2-Switched to twentyfifteen and still seeing error
3-Tried that card as well as a few others with expiration date 10/20 with and without cvc
4-Currently using UNMODIFIED plugin on live site with no issues

I am trying to test on my dev site in sandbox mode but I keep getting the following error “Merchant do not support accepting in unknown card”. I have an authorize.net sandbox account, I have entered the correct API ID and key, i tried in sandbox mode in your plugin as well as in live mode. I am using the Authorize.net card numbers on https://developer.authorize.net/hello_world/testing_guide/ and I have also tried my Authorize.net in test and live mode and I get the same error every time. Any suggestions on how I can fix it? I can’t test on my live site as it is a a busy site and I don’t want to break anything.

Thanks!

Thanks I will test it now.

I ran a test order and did not enter the CVC code and it let my order go through so I do not think the CVC field is actually required. I don’t want to hide the field, make it act like the phone number or email field; when it is set in the back-end to “required” it shows the asterisk by the field and if the field is left blank it shows an error at the top of the page saying the field is required or cannot be left blank or some sort of error notice. If in the back-end it is NOT set to “required” then the asterisk by the field is gone and it does not show the error notice when it is left blank.

I am more than happy to donate, let me know if these changes are possible and I will donate. Thanks for the help and support!