I would like to see the following functionality introduced into Drupal eCommerce Core:

  1. Site admin has the ability to specify a unique "thank you for your order" and "cancelled" page reference for each payment method
  2. If no unique "thank you" or "cancelled" page has been specified on the receipt type settings page, eCommerce picks up the pages specifed in the GLOBAL SETTINGS page for receipt types.

It's a fairly simple addition, but, I think it will be very useful, particularly for sites that want to provide payment options to customers that don't come with instant payment notification. In particular, bank transfers and cheque/bank drafts or some payment gateways such as CCNOW, which is popular but doesn't have an instant payment notification facility).

In other words, with the suggested functionality added, it will be relatively easy for ecommerce site admins to display a specific message for users who choose different payment options...that would require a different "Thank you" message.

For example, for bank transfers - it allows the site admin to display the necessary bankin codes along with a simple refernce ID the customer can use when making the transfer..(such as the TXNID with a text string (maybe the site name) to track incoming bank transfers to the shop bank account. Similarly, for cheque/bankdraft payment methods, specific instructions maybe displayed explaining how anmd who to make out the cheque/bankdraft for...and where to mail it.

I'm not sure whether it's more efficient to introduce a new hook to payment gateway modules or to include it in core but I'm guessing that it would be more efficient, code-wise, for to be done in core.

Anyone else have similar ideas/requirements?

CommentFileSizeAuthor
#2 ec_paypal.module.patch1.32 KBdublin drupaller
#2 ec_receipt.patch4.94 KBdublin drupaller

Comments

gordon’s picture

gordon commented

Yes this does sound interesting, it could be added to the options page and can be specified by the hook_receipt_types_info().

If would also need to be saved in the ec_receipt_types table as well.

If someone can submit a patch I would be happy to accept it.

dublin drupaller’s picture

dublin drupaller commented
Status: Active » Needs review
StatusFileSize
new ec_receipt.patch4.94 KB
new ec_paypal.module.patch1.32 KB

patches attached

notes:

1/ Have included an ec_paypal patch as well, which needs testing.
2/ difficult to test without the checkout working

maybe revisit this feature idea once the checkout is finished and working?

gordon’s picture

gordon commented
Status: Needs review » Needs work

This looks pretty good, except for a couple of things.

1. There is no update in ec_receipt.install to add these fields. (start update at 6400)
2. Neeed to create a function to get the return url for the payment gateway to call so that all payment gateways will use the same functionality without the developer needing to know too much.
3. need to also add some code to ec-checkout to also use this new function.

Gordon.

dublin drupaller’s picture

dublin drupaller commented

2. Neeed to create a function to get the return url for the payment gateway to call so that all payment gateways will use the same functionality without the developer needing to know too much.

yep. that's exactly what I was thinking..particularly when modifying the paypal.module.

That said, I didn't really want to create extra work for you...so perhaps it's best to postpone adding in this feature until the checkout is complete?

We can revisit it once the checkout is done - I can't really see anyone updating their payment modules for version 6.x-4.x before that happens.

What do you think?

gordon’s picture

gordon commented

I have been considering this more, and I think that using rules to do this may actually cover the requirements of this without needing to do all these changes.

This will mean that if someone wants to do this they can do this and more.

Let me know what you think.