If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
The customer Order Confirmation e-mails do get sent and are automatically triggered, but only after the order’s Amazon status goes from “new order” to “ready to ship”.
This can sometimes take days.
You can check what the Amazon status for an order is in admin. In manage orders, click on the order in question, and right under payment type there will be a field called “Status”
If it has a value of “new order” then Amazon looking the order over.
If it has a value of “ready to ship” then Amazon has accepted the order, and at this point the email will be triggered.
- I placed an order using CBA, which went through fine.
- MIVA displayed the OPRC screen.
- Amazon then sent an email 20 min later for Payment Notification....so far, so good.
- However, MIVA never changed the order status to: "
ready to ship", which also didn't trigger MIVA to email the INVC.
If it suppose to work as you described above, then it is not working and this is a bug <g>.
Are you certain Amazon has a communications mechanism back to MIVA to change an order status to "ready to ship" (20 min or days later!)? ...or am I missing a step?
Make sure your CBA settings are all properly configured in the Amazon side. If there unable to get back to the stub file in your Miva store to make the order as shipped, that could cause this issue.
What do you have your HTML declarations set to? I have all my sites as UTF8 and thus no issues.
If your HTML page headers are 1255 then forms will submit that data. There are conversation threads this forum about encoding types that explain why.
The character set in the store's settings is set to UTF-8, and all of the pages in my store are being served as UTF-8, both front-end and admin pages as far as I can tell (Chrome's developer tools are saying that the server is sending a Content-type of "text/html; charset=utf8" in all pages I've loaded, and Chrome is rendering the page with UTF-8 encoding).
The tokenlist module isn't showing the attributes structure when I've included the product_attributes item on a page. Yes, I've made sure that the product I've loaded in the token list has attributes.
The tokenlist module isn't showing the attributes structure when I've included the product_attributes item on a page. Yes, I've made sure that the product I've loaded in the token list has attributes.
chrisb,
I looked into this and it is in fact a bug in the tokenlist module. I have filed a bug on this and it will be resolved in the next update. Thanks for finding and pointing this out!
Ryan
Ryan Guisewite Lead UI Developer / Miva, Inc. www.miva.com
First backorder since switching to CSSUI. I put in a date of 10-01-2012 but now the order shows "Backordered: 4-11-1964". Not sure if this is a bug or just something to do with my store. Miva Merchant 5.5
Production Release 8 Update 6
Miva Merchant Engine v5.12
Database API: mysql
I'm not sure when this one crept in. A store is using the Miscellaneous Fee module to create a "Handling" fee. Everything is fine with the fee showing in the basket and then into checkout. It was even showing on the OSEL page. But after clicking Continue and landing on the OPAY page, the fee would disappear. After hours of head beating, I changed the fee from Handling to Handling Charge. The fee stuck and was not erased on the OPAY.
The problem is if you call the fee "Handling" the built in shipping rules/handling charges module removes the charge. I see this as a bug as it should only remove the charge if it's module ID is assigned to that specific charge. Other modules which apply a handling charge should not have their charges removed. Instead of deleting by type, it should be deleting by module_id. If one module removes another module's charge based on type (which could be similar across several modules, e.g. COUPON), there will be a wild west environment with lots of hours spent trying to troubleshoot the problems.
Comment