Active
Project:
Simple Cart
Version:
6.x-1.1
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
23 Dec 2010 at 18:35 UTC
Updated:
4 Feb 2011 at 16:24 UTC
Need order history or log.
it is desirable that the manager would be able to celebrate - whether the purchase is made on this proposal or not + comment
Comments
Comment #1
vladsavitsky commentedOk. I'll do this. Thanks
Comment #2
andypostThere's a similar approach from acart module http://drupal.ru/node/10113 => http://www.drupalka.ru/node/89 and http://www.drupalka.ru/node/97
Suppose you need to join forces
Comment #3
Hek commentedSubscribe. I need too order history.
Comment #4
vladsavitsky commentedThis is next in my todo list.
But I'm thinking about best architecture for this.
Orders can be special nodes or just store data in database and show lists in admin's area.
"Order as nodes" pros and cons:
1. We can use all power of nodes (hooks, build views and more).
2. Dificult for me to create this special content type with complex CCK-fields to store information about each item.
"Order as database record" pros and cons:
1. Easy to implement (for me).
2. But more code to build lists and all extra features should be coded by me.
Order as nodes seems to be better solution but I don't know to to simplify storing items info. For now I think this should be complex CCK-field: [noderefference] - [price] - [quantity].
Building this complex fields takes about one month (176h) so if you could suggest more simple solution - I'll be glad to do it.
Comment #5
Hek commentedI'm not very good expert in Drupal (and English). :)
For me, it would have been enough to create the "Order"-node, with contents of the cart as text in the body and text fields with information about the client.
Comment #6
vladsavitsky commentedOk. Task is create a module which creates nodes to store order's information.
Comment #7
Hek commentedAnd if use to create stories of orders already finished module Webform? This module is often used.
Comment #8
andyposthaving orders as nodes has disadvantage that they appears at content admin screen and they are visible to any user by default.
So +1 to it's own simple table (for D7 this could be an fieldable entity) and own admin section 'Orders'
Comment #9
vladsavitsky commentedIf order is custom content type defined in simple_cart module (or submodule) than we can restrict access to nodes and regular users will not see this nodes. Also using ACL (or similar) will allow to restrict access to order-nodes for given users.
Comment #10
andypostACL does not allow to hide nodes from admin/content also it brings some sensible overhead for all node queries so BIG -1 to nodes
PS what's about joining forces with drupalka.ru?
Comment #11
vladsavitsky commentedOk. Let 2.0 will be version where simple_cart and acart is joined.