Hello,

I like the concept behind http://drupal.org/project/payment namely that there should be 1 module that other modules can reuse. So, having an order module that is used by Commerce, Ubercart etc would be great. :) This would also attract developers that dont want a cart, just an order form. For example, users select some stuff in a views with checkboxes, and the next page they are taken to the order page.

Comments

jenlampton’s picture

jenlampton
she / her
CreditAttribution: jenlampton commented
Version: 7.x-2.0-rc1 » 7.x-3.x-dev
Issue summary: View changes
Status: Active » Closed (works as designed)

For starters, if you don't want a cart, then you shouldn't be using a module called "Basic Cart" :)

Unfortunately, modules like Ubercart and Commerce are very different, so it would be very hard for an "orders" module to provide the same features for both of them (they probably don't even have the same requirements or feature sets).

What may work for all systems is having a Drupal-native content or entity type that tracks your order data. This would allow you to build reports with views, and use all other entity and field modules as well. The 3.x version of Basic Cart is doing exactly that.

I'm going to mark this issue as closed (works as designed) because we are not working on a common ubercart/commerce/basic_cart order module.