Matt Rutledge
2018-04-03T19:01:52Z
When placing a new order when I process a credit card through Authorize.NET and the card is declined the user gets redirected to the cart page instead of an order page or the checkout page with a message saying the card is declined. I have been searching around trying to figure out how / where this redirect is happening and can not find it. I do have a custom order workflow in place. How can I properly let the user know the transaction was declined and allow them to attempt a new credit card or payment method for an order?
Will Strohl
2018-04-08T18:59:52Z
I'm afraid I'm not going to be of much help, because the default behavior here is to redirect the visitor to a modified version of the checkout view when a payment issue occurs. This view will present visitors with the payment issue message. You'll want to review your customizations to any extension point, including the viewset, custom order workflow, and action delegate.
Will Strohl, Upendo Ventures
Hotcakes Cloud  | Get Support  | Code Support 
Official Cloud & Support provider for Hotcakes
Matt Rutledge
2018-04-09T14:39:42Z
Thanks Will. I will test with a clean install of hotcakes so I can see the default behavior. I know I didn't do anything special with redirects in my workflow so must be something from a view or javascript that I have.
Matt Rutledge
2018-04-09T21:25:34Z
I tested using the default views and the default workflows and I am experiencing the same issue. When looking at the cart controller on github I see the Checkout PaymentError Action checks the following:

if (CurrentCart == null || CurrentCart.Items == null || CurrentCart.Items.Count == 0)
{
Response.Redirect(Url.RouteHccUrl(HccRoute.Cart));
}

So by the time it gets the declined error on the card it has already placed the order and cleared out the cart, it then redirects me to the cart instead of the payment error page. I am on version 3.0.1

This is what I have for my LoadProcessNewOrderTasks (which is the only workflow step that happens before the Payment steps) I believe the only difference from the default is that I am doing a CustomDnnCreateUserAccountForNewCustomer step:

return new Task[]{
new WorkflowNote("Starting Process Order Workflow"),
new UpdateOrder(),
new CheckForZeroDollarOrders(),
new CustomDnnCreateUserAccountForNewCustomer(),
new AssignOrderToUser(),
new AssignOrderNumber(),
new MakeOrderAddressUsersCurrentAddress(),
new AddUserAddressesToAddressBook(),
new UpdateLineItemsForSave(),
new UpdateOrder(),
new MakePlacedOrder(),
new UpdateOrder(),
new WorkflowNote("Finished Process Order Workflow"),
new UpdateOrder(),
};
Matt Rutledge
2018-04-10T21:37:36Z
I have added a bug on GitHub for this issue. It includes reproduction steps and a suggestion for a fix.

https://github.com/Hotca...Commerce/core/issues/120 

Will Strohl
2018-04-19T20:44:43Z
Thanks for your work on this Matt. I plan to include your update in the 03.02.00 release. I hope to push that release by Monday.
Will Strohl, Upendo Ventures
Hotcakes Cloud  | Get Support  | Code Support 
Official Cloud & Support provider for Hotcakes
Kurt
  •  Kurt
  • 78.25% (Friendly)
  • Member
2018-04-20T05:32:54Z
Which bug fixes are pushed with the 3.2 release. And are there new features?
Will Strohl
2018-04-20T19:58:04Z
You'll always be able to see this by looking in GitHub:

https://github.com/Hotca...ommerce/core/milestone/4 
Will Strohl, Upendo Ventures
Hotcakes Cloud  | Get Support  | Code Support 
Official Cloud & Support provider for Hotcakes
Loading
  • Sign-up for the Hotcakes Community Newsletter: