Olá dev_cw
It is my understanding that you are envisioning a Wizard type application to build a sling. There is one model of sling and what changes is the fabric and I guess the size? The client chooses 2 fabrics per sling, inside and outside?
Right!
I am thinking that a fancy form with steps would be cool having a step for selecting the fabrics then the size and etc... Since it seems that the fabrics are the key element I would set up one MODx document per fabric and set up the fields you need including a value. Then you could use Ditto to present the fabrics in the ’Wizard’. Exactly how to do this will depend greatly on your approach. One idea would be to have an pulldown type menu and some ajax to load the images. But there are quite a few alternatives as well.
If I understood you correctly, a form will lead the user through a series of steps. If this can be done on a single page, that is what I want. Otherwise the wizard will be an annoyance.
I have thinked about this a bit more, and maybe the attached image helps understanding what I want. Below a main area are two distinct areas, each containing the thumbnails of all the available fabrics, like in, for example,
http://www.flickrleech.net . Clicking on a thumbnail will populate the region of the main area directly above the list with the corresponding image.
Would Ditto be able to build the thumbnail area? Maybe piping it through mootools will fix this? Am I talking nonsense here? I have been consulting the docs but... well, I do not even know where to start.
Actually there is only one item, the rest are only characteristics (no different from when you order a shirt and select a color and a size). The order process will need to calculate the item price based on the optionals and then add all the specs to the cart.
I get it - another level of abstraction here would solve the problem: I could create a list of
fabrics rather than products and sell only a single product, with many variations. Which is what happens in reality. Right? But how would you integrate such an extended list of characteristics with a single product?
To track the origin of the order you could track the referrer as banal suggested, possibly combine it with a cookie to be able to track the visitor beyond the first page they visit.
So, imagine that my site is A and the referrer is B. My aim is to know whenever someone goes from B to A and in the process buys a sling. This can happen in two ways: in a single session or in multiple sessions. The former seems easy to figure out, but the latter seems tricky to me. In any of the ways, the visitor may - and in most cases will - stroll through several pages before actually committing to buy. I gather from your words that in any of the cases, I need to use a cookie to track the visitor through the pages he visits. But in the second case, I need to know that he is returning, and not merely a new visitor, even if he directly types the URL to A in the browser address bar. Do cookies allow me to know this on top of the random-walk?
Also, the multiple session gotcha may also require me to determine if the following is happening: is a user coming from B to A known to have been previously visiting A? Is this too much detective work. Is this possible?
Again, thank you for your pointers!
João Paulo Magalhães