AbleCommerce Shopping Cart Software

I never noticed before that members do not use the OnePageCheckout. I am not sure what exactly changes whether they use one page checkout or not, but it seems like if they have a valid shipping address stored then they get redirected to "Select Shipping Address" instead of onepagecheckout.

Many of my customers are not going to be shipping to themselves and also may be entering a large volume of delivery addresses so it might be innapropriate for them to select a shipping address using this page ~/Checkout/ShipAddress.aspx.

How to I make a member still use the OnePageCheckout (~/Checkout/Default.aspx)?? instead of (~/Checkout/ShipAddress.aspx)??

Please help.

I thought that changing this file App_Code/NavigationHelper.cs on line 204
if (hasValidAddress) return "~/Checkout/ShipAddress.aspx";
to /Checkout/Default.aspx might work, but I really do not want to break anything or make changes that might be overwritten by future updates.

This problem just arose for me also, but I was waiting until Monday to post it. Upgraded to 7.0.2 and like you say, if a customer is logged on, they go a different checkout route. Which might not be bad, but this site has customized shipping method code that we have already put on the one page checkout and the shipping estimator. I hate to go back to the merchant and say, well Able changed the checkout flow and it's going to cost you more. If we could just disable the new flow, it would fix the problem. I was really surprised at all the changes in the upgrade- I had to change quite a few places, like everywhere in the custom conlibs that had the old code for registering the pageviews.

I think I've found a setting for this- I changed it on one site and so far only the one page checkout has come up.
On the ConLib basket.ascx.cs, change
Response.Redirect(NavigationHelper.GetCheckoutUrl());
to
Response.Redirect(NavigationHelper.GetCheckoutUrl(false));

In the new App_Code/NavigationHelper.cs, there is code for that to send the logged-in user to a different checkout flow.

Don't forget to change the checkout code on the minibasket also.

Thank you for the information Judy. I will try this change out.... hopefully it works. It is a good solution because a custom basket conlb can be created so the change isn't deleted by any future updates.

If anyone has any concerns, ideas, and/ or thoughts as to why this change will not work of might have a negative impact on the application please speak up. Thanks!

The merchant has checked out the site I did the change on, and he says it works fine.