AbleCommerce Shopping Cart Software

Ok...let's see if I can explain this clearly.

I created a Cancellation Notice. The content is basically a modified copy of the Customer Order Notification email.
I set it up to send to the customer, with a BCC to our email address.
I checked off for it to automatically generate when order status is changed to canceled.

Screen shot of these settings:

I also went back under Order Statuses and added the cancellation email to that change of status, but this did not make any difference to the testing before or after I did so.

I selected one of my test orders and changed it's status to Canceled.
NO email was generated for either address, mine or the test customer address.
Once canceled, I could not manually send ANY email through the system for that order. Trying to change the status back to pending, etc., did not make any difference.

I could go to a different order that was active and manually send the cancellation email to that email.
Each time I did so manually on the un-canceled order, the customer email address received not 1 but 2 copies of the cancellation notice. I think this occurs because it's adding the email from the order screen in addition to adding the email in the email form using the keyword "customer"? I have no idea how to fix it that particular side issue.

The basic confirmation email when an order is placed works fine, as does the automated one that kicks out when the order is marked as shipped in the shipping section.

Changing the order status using the Task dropdown menu in the Order Summary seems to the be problem? It's not generating the emails.

Anyone able to help? Thanks

Mizmo67 wrote:Changing the order status using the Task dropdown menu in the Order Summary seems to the be problem? It's not generating the emails.

To my knowledge, email triggers are not fired when you manually change the order status. They only fire when a specific Able function or menu choice affects the order. For instance, shipping all items on the order automatically marks the order as "shipped" and thus the order shipped trigger will fire. However, manually changing the status from "Unpaid" to "Shipped" will *not* fire the same trigger.

Use the Cancel Order on the Order Summary page and cancel the order that way. Then the order cancelled trigger should fire.

Thank you, Joe.

It's making me nuts. That IS the page that I'm using.
I select Cancel from the dropdown menu on the task bar in the summary page.

So why is it not working?

Wow that is a good question.

All you should have to do is assign an email template to the Order Cancelled trigger. Sounds like a trigger bug to me but I'd have to test it on my site. I'll see if I can do that this weekend.

Its working for me. Make sure that you haven't any error in the NVelocity code. For a test create a very simple Email template for example with no NVelocity code having some text message like "Order Canceled". Attach it to order canceled event and then give a try to it.

Back to working on this problem.

I tried creating an email triggered by Order Note Added by Merchant.
I removed all the NVelocity codes from the template ($store.Name, etc)

I still get 2 copies on the receiving end instead of one.

I've noticed that the problem is occurring about 90% of the time. Occassionally I only get one message, but mostly it duplicates.

It looks like I have everything set correctly, I can't figure this out?

If you're setup to BCC yourself with email templates and you're testing it with your own store account, you'll get two copies.

I forget that sometimes and spend a few minutes scratching my head before it finally hits me

In AbleCommerce 7.0 version, when some one tries to send Email directly from order page then it sends duplicate Emails. Please check the following thread for a work around.
viewtopic.php?f=42&t=9319
This problem is fixed in 7.2 version and its fix is available in 7.0 to 7.2 upgrade, check the
6997 minor sending email directly from order page is duplicated
entry in change log.

Thank you! Both of these answers help tremendously. I was worried we were going to spam our customers when this thing goes live, lol