How can I "do something" after a successful PPE order?

I thought you guys were continuing the discussion on a theoretical basis, but if there's still concern for my application (thank you) I had it working @ post 24 above.

Quote:

---

Originally Posted by s_mack

After looking a little more carefully, I think I've settled on NOTIFY_HEADER_END_CHECKOUT_PROCESS

It gives me all the vars I need, it happens after function after_process() is called (which is what the payment modules uses to update the history), and I think it is tight enough to not have to worry about refreshes. I tried refreshing and there was no ill effect that I could see.

Does that sound right?

---

Quote:

---

Originally Posted by lat9

The notifier you chose (NOTIFY_HEADER_END_CHECKOUT_PROCESS) will do the trick for you:
1) It's at the absolute end of the checkout_process processing, just before the redirect to checkout_success.
2) It's not a page that is "easy" to refresh, since it's never visible in the customer's browser.

---

Thanks to both of you, your suggestions have helped me to implement something similar on one of my local dev sites.

Quote:

---

Originally Posted by s_mack

I thought you guys were continuing the discussion on a theoretical basis

---

I was/am.

Mainly to get ideas - whether they be sound, practical, efficient, best for purpose, or whatever. It's all good IMO.

I see as a result of this thread we already have one person (frank8) that has taken the idea(s) to do something on his own site(s) -
Something that may possibly never have eventuated otherwise.

The choice of HEADER_START or HEADER_END (or both) is certainly going to be dependent on what is needed and what data is available for that need, and with all that is currently known, I too would say that you have made the right choice for your purpose. I might even go as far to say that I may have made the wrong choice for the purpose of the ec_commerce module.

As a result of this discussion, Frank, and others that follow, have the benefit that neither you or I had when we started our projects - We've covered three possible notifiers (and a combination of them) that *could* be used for a purpose, and we've revealed the benefits and pitfalls for each, and the one instance that wasn't a good choice for the need (the NOTIFY_CHECKOUT_PROCESS_HANDLE_AFFILIATES).

It has been (and is) a good discussion even though the initial 'problem' has been solved.

Cheers
RodG

Agreed Rod. I just wanted to be clear that I wasn't still waiting for help :)