Coupon code autofills in checkout on return visit

This also happens on my site/s at 3.9.4.

If you erase the coupon from the checkout page, click update coupon the page shows the discount gone BUT after the purchase is done the transaction results and sale log show the coupon was actually applied.

As deactivating the coupon from the WPEC back-end causes the ‘price before shipping’ line to disappear off the checkout page I’m circumventing the problem by using CSS to not display the coupon line.

Fortunately we don’t generally use coupons.

As a temporary fix I created a new coupon called “No Coupon” with a value of $0.00 and added a new button labelled “Remove” next to the coupon field. When clicked it will apply the “No Coupon”, which resets the cart back to normal price. It’s a bit of a hack but it works.

In the meantime I’ve just about finished migrating to Woocommerce. It is so much better than WP eCommerce.

Hi ozoneboy,

Glad to hear you’ve found a different solution that works for you.

Toshi,

This specific issue will be fixed in our upcoming 4.0 release. You can see the actual change we made here:

https://github.com/wp-e-commerce/WP-e-Commerce/commit/98d0727e89a174faeccb375415010758f986a50f

Hi Justin,
Thought I’d offer some constructive feedback regarding my decision to switch.

I feel like your steadfast choice to always remain backwards compatible has caused a lot of compromise and complexity that probably takes up a lot of your time putting out fires, time that could have been spent developing something great. If you try to please everyone, you end up pleasing no one.

Woocommerce is relatively new, built from a clean slate, and lots of developers are supporting it with great plugins and the documentation is excellent. Of course I’m sure I will discover it’s flaws at some point but first impressions are impressive. I see you’ve been contributing to their development too so I’m sure you’re well familiar with the product and could enlighten me on any shortcomings?

My main turning point was the issues I’ve had with the checkout form. It’s been a nightmare. Unfortunately you didn’t follow it up so I assume you’re focused solely on 4.0 and theme engine v2? I saw a comment on Git from Dan suggesting the sooner you ditch theme engine v1 the better, so from that point I lost a lot of confidence and unfortunately can’t wait for v2 to be released and all the bugs ironed out.

I still have another client using WPEC so I’ll keep an eye on the updates and see how things develop, but for now I’m going to give Woo a damn good test.

Hi ozoneboy,

As you said, you’ll likely find any shortcomings WC has on your own, so I won’t bore you with my perceptions. So much of that is in the eye of the beholder, anyway. For example, one report I’ve heard from many is that their documentation can be quite lacking. I’d say the same of ours, but you seem to like the documentation they have – so it’s all quite subjective.

I do appreciate the constructive feedback – that’s super helpful! While our commitment to backwards compatibility won’t be changing, I definitely hear where you’re coming from. I hope you’re able to give our 2.0 theme engine a run with your client on WP eCommerce and consider it again for another project when it comes out.

Cheers!