I needed some time to solve the issue with the double-mailing on my installation, which was TODAY - JUCHUU. Yet I am on vm_sr 2.6.12_2 and jmlo 2.5.27.
I post my solution here, because other may profit from my research and test but I have to say, if I would have read carolmarkersons post in detail - there was the solution ... so thank u carol!
I think the double-mailing issue started with my installation on vm 2.6.8c. After that update I´ve had the above described double and partly incomplete mailing when ppl were ordering (same order).
It´s important to understand for my story that I came from a migration from vm1 and did the following after it: While started with migrated vm2-shop I remember, that I once deleted at vm-admin-BE one of those predefined orderstates named "confirmed by shopper" and I think it was with STATUS-CODE U in origin. I did not understand the meaning of confirmed by shopper and for what I should use it. For me I used the status-code P and renamed the origin from pending to order-entry-confirmation or in german "Bestelleingangsbestätigung". For me, this state should be first notification for shopper and vendor for all incoming orders and it worked this way, because we used a lot of payments which proceed after delivery, for e.g pay on delivery in german "Nachnahme", so pending in my understanding, stands for "user-confirmed but not confirmed from vendor". The next step - because I both sell things on stock and things I have not on stock which I order on demand - was to proof the availabiltys and if necesssary by on-demand-article-orders the stocklevel from the supplier. If the proof was successful I confirmed the orders with with an extra state which I call order-confirmation or in german "Auftragsbestätigung", besides this is the moment where the contract between user and vendor is finally made.
What did I done to solve it in fact?
- I added a new (once deleted) orderstate with order status code "U" and gave it the name I used for "P" -> "order-entry-confirmation - Eingangsbestätigung"
- I edited my old "order-entry-confirmation - Eingangsbestätigung" state (P) and renamed it to "pending - wartend"
- I edited my own language strings which will be included in the orderstate-emails with easy if clauses depending on the order status code. so I´ve had to switch from "P" to "U" in mail_html_shopper.php and in my language files
- I edited and changed all payment-options to reset the old order-state-references and set the new ones. I used "pending - wartend" only for cancelled paypal-payments!, all other payments with oustanding payment (PrePaid, Invoice, Pay on Delivery, Takewith ...) starting with the new "order-entry-confirmation - Eingangsbestätigung" with order-status-code "U".
(my options in vmconfig at admin-be: for every orderstate I sent emails to vendor and shopper but not "pending-wartend" "P" | no Option for invoices: I don´t use em)
Result:
Now vendor and shopper get no double and incomplete (payment- and shipment-data) orderemails anymore and it works this way. Only cancelled btw. not finalized payPal-payments have the pending state where no email will be sent. I am so happy.
My Conclusion:
Why did all this occured? In my opinion - and I say that not as an professional - it has something to do that you can´t use P for a normal-orderstate which is included in your order-state-email and payment configuration after vm 2.6.10, so it´s not a bug but a possible user-based missconfiguration. RTFM ! Maybe it would have been better if I have read the ***obscenity removed*** manual ... lol
greetz to you all
jens
[attachment cleanup by admin]
Home
Forum
Extensions
Developer Portal
