e-Commerce Module

1. Redirect to a node dependant on product purchased.

2. Add to or alter the "payment completed" message per product.

I would think there is a relatively straightforward way of accomplishing these objectives, but I can't figure it out...

Any ideas?

I've managed to completely translate E-Commerce modules to German. Translation is based on 4.7 and needs a one-liner-patch to cart.module (missing t()-function). So now I've got 9 gettext files and 1 mini patch I'd like to contribute.
After several hours of translating, testing and translating I don't want to create one issue for each file, so can I please mail them to someone to commit them? (gordon?) I doubt I should use the file attachments here. So please come by and help me to get this in!

My motivation is to get more German users to E-Commerce. Drupal with E-Commerce is a fantastic solution compared to other online store systems like osC, xtC, JOS VirtueMart and so on. Altogether we have to remedy some major deficiencies in E-Commerce, f.e. the incomplete tax system and some legal rules we have to implement for usage of E-Commerce in Germany/Europe and even more important for selling internationally (different currency and tax per language and the like).

Hello again. :)

Does anybody have an ideas as to how to attach a note to an online donation?

i.e. user fills out an amount, wants to specify that it be earmarked for the Social Fund or whatever.

I thought I could product-enable a survey (using the survey module) which had a little field for notes, but I couldn't get that to work.

Any ideas?

Thank you.

--D

The new form API has some terrific features for Ecommerce. Specifically, I think the checkoutapi can be fully removed. In its place, we do one form with #multistep = TRUE. Default ecommerce will have a couple pages in that form just like we do today. Contrib modules that want to hook into checkout do so with hook_form_alter(). Seems cleaner IMO.

There are probably other opportunities, but that one jumps to mind first.

Hi
In advance, my apologizes if I'm not addressing to the right place this comment of mine, I'm quite new on Drupal world and , therefore, on E-commerce.
Just Today evening I installed Drupal, and E-Commerce , with PostgreSQL instead MySQL.

After Installed the E-Commerce Module I started to get errors in the Log

query: INSERT INTO ec_tax (realm_value, realm, ptype, operand, operator, taxid) VALUES('fr', 'country', 'file', '+', '6.00', '')

Reviewing the postgresql logs I see that

ERROR: relation "ec_tax_taxid_seq" does not exist

So I searched in the file tax.install

I'm very much hoping this isn't a feature request for 4.8... I'll just explain my situation:

I'm making a fundraising auction site for a nonprofit arts center, and really all I want to do is add some attributes for the volunteers adding items to fill out in addition to the description, that is, have a field to enter the name of the person who donated the item, and another field for the estimated market value.

I thought it would be trivial to create my own product type based on the auction module and with an extra field or two, but it has not been!

I can see many reasons to add open-ended text fields in addition to one big block for "description" to products, so I hope someone has some experience or advice.

Drupal E-Commerce module currently support for single currency only. This means all of your products can only base on a signle currency format, within DB, for customer browsing, for transaction, and also for accounting. This will be a trouble, if you hope to setup an auction system as like as eBay, or even simply hope to use Paypal module in where local currency is not support. The need of multiple currency supporting is clear.

By the way it is also a complex problem (from http://www.xencraft.com/resources/multi-currency.html) :

when redesigning the software to accommodate different or multiple currencies, the designer should be careful as to which aspects are determined either by user preference (which may in turn be indicated by locale), by regulation, by the nature of the application, or perhaps by other factors. The appropriate determining value(s) will need to be a part of the API.

UPDATE (Jan 11): Code has been moved from the sandbox to ecommerce CVS pending full integration with the ecommerce system. I'm currently writing upgrade code to move products and the transaction records over to the new format. NOTE: If you are migrating custom solutions you will need to take special care with the upgrade. You may need to manually update the schema revision field in the system table to skip the upgrade and apply your own code instead.

Once the upgrade code is complete i'll be removing the old code from ecommerce. After this i'll send a mail to the ecommerce list to ask for testers.

You can get a copy of the alpha code by using the CVS tag DRUPAL-4-7--3. Alternatively download the tarball.

UPDATE (Oct 12): Thank you to the financial contributors. Code for all modules is now available in my sandbox. Please keep in mind that the code is still in beta and no upgrade code is available for you to upgrade your current 4.7 sites. It is not recommended that you use this code in production. Please post all issues to the Drupal issue queue and it would be very handy if you provided patches. I'd like to get hold of some anonymized production databases using the 4.7 default recurring product system. It'll help me build the upgrade code.

UPDATE (Sep 30): Still waiting on financial contributors. The ec_anon module is ready for trialling. It's available in my sandbox.

UPDATE (Sep 22): I'm excited to announce ec_recurring, ec_roles and ec_mail modules are ready for testing. There is a slight delay on ec_useracc due to some extra feature requirements on EC. That should be available very soon. Financial contributors please forward your second instalment and contact me to obtain code.

UPDATE (Sep 04): Feature Freeze in effect as of September 4, 2006. No more features will be added.
Scheduled UAT date: September 22, 2006. Scheduled completion date: September 30, 2006.

Hi everyone,

I've just finished writing up a specification document from which developers can see what is planned for E-commerce in relation to subscriptions, roles and user accounts being manipulated during checkout. These are highly sought after requirements and many people are scratching their own itch scratch scratch. My aim, though providing a specification document, is twofold. First, I want to make sure everyone knows what we're developing for 4.7 and then for 5.0 (after we do some major changes to E-Commerce core). Second, it provides a solid reference for any developer planning to write anything.

Hi guys,

I recently updated the worldpay.module for 4.7 and included an automated "callback" after the order is processed...i.e. the worldpay server tells the drupal site that the transaction was either APPROVED or CANCELLED (Denied happens at the worldpay end and the order is cancelled).

So a Drupal site admin who is setting up their worldpay enabled shop, enters in the worldpay_callback the worldpay server sends the "y" or "c" flags to. The problem is securing that transfer of information or in other words, validating the source.