I've been muddling my way through my first Drupal/e-commerce project, and I've managed to get my large list down to just a small handful of questions. If anyone has some guidance for me on any of them, that would be great. just as some background, I'm quite familiar with e-commerce in general, having used osCommerce, ZenCart, Xcart, and others quite extensively, but I'm not wrapping my head around this one for some reason. I'm also a Drupal newbie, but not a CMS newbie. We're running E-commerce version 3, on Drupal 4.7.
-
I'd like to customize the /product page layout. I think I need to create a .tpl file in my theme for this, correct? How do I get the proper variables, and how do I tell it where to look for such a thing?
-
Does anyone have any guidance on creating a payment module? I have the exact code that I use elsewhere to post a donation transaction from a form to our processor's website, but I'd like to integrate this into the Drupal structure properly. I've been working from the eway one, and I have it connecting properly with hardcoded info, but things progress very slowly. :-)
-
Why is the credit card infomation on a separate page, after you say you've placed your order? On the "review" page, it just says "Payment - credit card", with no ability to put in anything. You have to click "Place your order" first, and then it asks for cc info. This is very non-intuitive to me. Has anyone experimented with putting those fields directly in the checkout process somewhere?
Thank you!
Comments
I'd like to customize the
See http://ecommerce.heydon.com.au/api/function/theme_product_view_collectio... which will show you how to re-theme this page.
Look at the paypal/ccard gateways I think they are the most up to date. In the future I want to develop a page on the ecommerce.heydon.com.au site which has more information about doing this.
This is because of the structure of the system currently. As the payments connected directly to a transaction and not a receipt, and at the point of accepting the review page, there is no transaction created. This means that if there is a crash we can loose the payment details.
In future we are going to have the payments create a receipt and then have the receipt allocated to the transaction which will mean we will be able to take the payment on the review page.
Receipts will be coming in the v4 development, but I don't know about have the payment collected at the review screen.
--
Gordon Heydon
See
Brilliant! I'd been trying to sort through the API pages, but it's slow going, and I've got people breathing down my neck on this one.
Ah...I found a post in my google searching (from this site's accompanying list, I believe - here's the link). It mentions that ccard and eway are both using the newest method. But I'll take another peek at ccard and see if there are any differences.
Thanks for the explanation, although I think it'll take me a bit to get my head around it. :-) I'll likely be inserting some text (and it might not be a bad idea to do it in the default install) that says payment details will be collected on the next page, or something to that effect. It's a bit confusing to a consumer who's more used to traditional shopping cart models.
Anyway, thanks for the help! And if you have any further advice on the payment module, I'm all ears. Otherwise, I'll continue hacking away. I know I read something about modules having to be confirmed by numerous people before they could be used - would it be worthwhile for me to make my code available anywhere once it's done?