From a default install the transactions are not being sent out correctly, or to the correct address
--8<--
Dear Customer,
Thanks for your recent purchase from Drupal. This message includes important information about your order. Please take a moment to read it closely, and be sure to save a copy for future reference.
********************************
Billing and Shipping Information
********************************
Shipping to:
Shipping service:
none
Billing to:
********************************
Order Details
********************************
[items]
Questions about your order? Please contact us at
********************************
Shipping Instructions
********************************
We will notify you by email as soon as your order ships.
Thanks for shopping at Drupal. We hope to hear from you again real soon!
http://drupal5.heydon.com.au
--8<--
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | store_13.patch | 1.54 KB | thekenshow |
| #2 | store_token_bug.patch | 8.17 KB | sym |
Comments
Comment #1
neclimdulMarked #113293 duplicate.
From the post:
Comment #2
sym commentedI've changed $values['[txn-bill-plus-ship]'] to $values['txn-bill-plus-ship'] on all of the tokens, and it seems to fix it.
Comment #3
sym commentedthis is a bug with the store module
Comment #4
bones commentedThis does not fully work, some parts of some of the emails get sent correctly but not all.
With the default emails:
Cancel transaction works
Ask customer works
Shipping notify doesnt
Invoice Doesnt
The site variables always seem to work (such as site-name and email).
Comment #5
sym commentedyep, after more testing this doesn't seem to work as I though it did.
Comment #6
thekenshow commentedI've found two transaction notification problems, for initial invoices and errors. I'm not up to creating a patch, but here's the relevant code with the errors commented out and followed by what works:
Comment #7
thekenshow commentedThis patch fixes the invoice, error and shipping email sending so they have the correct sender and content.
Comment #8
thekenshow commentedI just realized the version for this thread is HEAD, but the patch I submitted is for 4.7 v3b2.
Comment #9
bones commentedThis patch works great. Thanks
Comment #10
gordon commentedThis has been fixed.
Comment #11
bones commentedWhen has this been fixed? it is still apparent in 4.7.3
Comment #12
(not verified) commented