Recently one of the FB list members published a custom tag for handling
"wizards" which is one way to think about the shopping cart multi-fuse
process you were describing. Although his solution is just as good,
personally I prefered the wizards technique described in Jan 2000 CFDJ,
which had nothing to do with Fusebox but which was easily adapted thereunto.
You just give it a list of urls and there you go, it uses WDDX to store
progressive info on the pages as you go through each step and you can
back-up each step easily as well.
Another thing you could also do to stop the person from somehow jumping
"out" (tho I cannot yet think of how that is any different from the 93% of
web shopping carts that get abandoned before the final step is reached)
would be to save the "next" step as part of <CF_ReturnFuseaction> (or
CF_ReturnStack if you prefer the Churvis solution). But i don't think it's
worth the effort if you're using either of the Wizard solutions since
abandonment of the process can be handled many different ways.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
