Developer forum

Forum » Ecommerce - Standard features » epay - CheckoutDoneOrderIsComplete event not fired

epay - CheckoutDoneOrderIsComplete event not fired

E-mail notifications
Kenneth Radoor
Reply
Posted on 09/10/2015 12:34:46

As the subject say, it seems like the CheckoutDoneOrderIsComplete event is not fired when using the "epay - payment window" checkouthandler.

Looking at the log we do get the callback from epay, containing  the transactionnumber, so that is fine, and the order do get set to completet in DW.

I just missing the notification, so i can do a bit of extra work :)

Solution is runing on DW version 8.6.1.16

/Kenneth

 


Replies

 
Nicolai Høeg Pedersen
Posted on 09/10/2015 13:59:54
Reply

Code looks good at first sight.

What happens if you change your payment to a payment not using a provider (like invoice) so no gateway is used. That also fires that notification.

Capture.PNG
 
Kenneth Radoor
Posted on 09/10/2015 14:38:07
Reply

when no gateway provider is used, then all is ok.

/Kenneth

 
Nicolai Høeg Pedersen
Posted on 09/10/2015 14:52:42
Reply

What does the log on the order says in ecom admin? It will have a list of events, one of them "Order is complete" - do you have that event on the order where you have ePay?

BR Nicolai

Capture.PNG
 
Kenneth Radoor
Posted on 09/10/2015 16:14:31
Reply

should be there

The solution is http://kinovox.net.dynamicweb-cms.com/ 

Capture.PNG
 
Nicolai Høeg Pedersen
Posted on 09/10/2015 17:26:46
Reply

Hi Kenneth

Indeed it is there. Which also indicates it has been fired... See attached code.

Can I get a copy of your subscriber?

BR Nicolai

Capture.PNG
 
Kenneth Radoor
Posted on 09/10/2015 18:11:56
Reply

ok, 

the souce is in the solution i mailed you the other day. so its from our sample liveintegration project

 

 
Nicolai Høeg Pedersen
Posted on 29/10/2015 15:09:10
Reply
This post has been marked as an answer

For reference, the CheckoutDoneOrderIsComplete notification is fired, but handled by the callback. In the callback there is no context (i.e. pageview or user context) so that is something to be aware of in the notification subscriber code.

NP

Votes for this answer: 1

 

You must be logged in to post in the forum