Log of /contributions/modules/order/order.install
Parent Directory
|
Revision Log
|
Revision Graph
Revision
1.5 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Wed Aug 5 19:02:15 2009 UTC
(3 months, 3 weeks ago)
by
vauxia
Branch:
MAIN
CVS Tags:
HEAD
Changes since
1.4: +12 -71 lines
Diff to
previous 1.4
Beginning to refactor: An ecommerce Order is an instance of pay_form_order,
which is a subclass of pay_form. Thus, all of the configuration, available
payment methods, etc. are managed by the payment API, while 'cartiness'
is Order's sole domain.
Also, decoupling order_product items from nodes. There's no longer a 1:1
relationship between nodes and products: Product definitions will be class-based
and have an (optional) one-to-many relationship from nodes. For my current needs
I will write a "simple" 1:1 node:product handler, but there's no reason you
couldn't write some fancy sub-product backend later.
P.S. There is no - and will be no - upgrade path from any previous/current
version, until there's a downloadable dev release.
Revision
1.1 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Wed Dec 6 19:52:21 2006 UTC
(2 years, 11 months ago)
by
vauxia
Branch:
MAIN
An alternative e-commerce system. Orders are saved as nodes so that they can more easiliy be integrated into Views and use other Drupal features.
Order is a self-contained module that provides cart and order functionality. Additional modules can adjust prices and item contents through order_cart_alter() hooks. After rules are processed, the cart is saved as a node.
Payment processing will ship separately from this module, and will operate independently (e.g. a donation system that doesn't need full-blown cart functionality).
There's more to come, and this is pretty rudimentary. Input is welcome, but don't try running this on a production system yet!
This form allows you to request diffs between any two revisions of this file.
For each of the two "sides" of the diff,
select a symbolic revision name using the selection box, or choose
'Use Text Field' and enter a numeric revision.