Help!
I've just started getting orders with low order numbers come through via email. It looks like they're the orders which were never completed, but rather than disappearing from the database or whatever they're supposed to do, they're changing to live orders, complete with email to me and the customer, even though payment hasn't been made.
How can I fix this? I'm using 1.2.9, customers are paying via standard Paypal module.
Is there a manual somewhere where it states what the default should be in those boxes?
In paypal setting I have it as
Order Status: Processing (should it be processing or complete?)
Order Status pending: pending
Order Status Denied: Denied
Order Status Failed: Failed
..........
My concern is the Order Status?
In paypal setting I have it as
Order Status: Processing (should it be processing or complete?)
Order Status pending: pending
Order Status Denied: Denied
Order Status Failed: Failed
..........
My concern is the Order Status?
Opencart User
Well i think the fact that the order statuses match their exact status seems moot.
Order status Failed = Failed
Order status Processing = Processing
Order status Canceled = Canceled
its redundant. What else would failed be? It would never be processing. Canceled would never be pending.
It made sense back when you had the Ajax confirm setting it to the store default.. which was usually "pending"
Pending means that the order was "in progress" but the final payment hasn't been confirmed.
Then the payment single entry for "final order status" would be set to "Processing" to alert the store owner that the order was ready to be processed and that payment was completed.
It was simple and effective.
The problem that most people had was that the email went out on the ajax confirm step. My personal opinion would be that the email shouldn't go out until the payment is confirmed to cut down on confusion.. but others might have other ideas.
I'd also recommend handling the client side return in the callback as well. This gives you redundant protection, so that even if the IPN failed, when the customer returned back to the store, it would process it anyway. Like a fallback. Just code it so that if its already confirmed, don't confirm it again.
Order status Failed = Failed
Order status Processing = Processing
Order status Canceled = Canceled
its redundant. What else would failed be? It would never be processing. Canceled would never be pending.
It made sense back when you had the Ajax confirm setting it to the store default.. which was usually "pending"
Pending means that the order was "in progress" but the final payment hasn't been confirmed.
Then the payment single entry for "final order status" would be set to "Processing" to alert the store owner that the order was ready to be processed and that payment was completed.
It was simple and effective.
The problem that most people had was that the email went out on the ajax confirm step. My personal opinion would be that the email shouldn't go out until the payment is confirmed to cut down on confusion.. but others might have other ideas.
I'd also recommend handling the client side return in the callback as well. This gives you redundant protection, so that even if the IPN failed, when the customer returned back to the store, it would process it anyway. Like a fallback. Just code it so that if its already confirmed, don't confirm it again.
Who is online
Users browsing this forum: No registered users and 10 guests
