numero = 67119
interpreted = N
texte = I've found a PHP store with this functionality, but it uses a PHP function (explode) for which I can't find a WebDNA equivalent. Basically, they have a separate table for product options. They delimit each option within a field with "->" (tabs added for readability): optionidproductidskunameitems 11123MW->123LW->123XLWSizes - ColorsM - White->L - White->XL -White0.00->0.00->1.00 They use the explode function to create a pulldown menu like this: Could a WebDNA function be written to split this single record into individual items? If so, any pointers would be helpful as I've written a function. On 5/9/06 11:21 AM, "Clint Davis" wrote: > I'm setting up a new store with some products requiring size/color options. > I noticed that StoreBuilder does this, but I don't like the implementation. > StoreBuilder assumes that every size is available in every color, but that's > not the case in my store. I may have red, blue, and green with sizes small, > medium, and large, but the red shirt is only available in small. > > I'll store options in a separate database, but I'm interested in how > everyone else handles this? ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
I've found a PHP store with this functionality, but it uses a PHP function (explode) for which I can't find a WebDNA equivalent. Basically, they have a separate table for product options. They delimit each option within a field with "->" (tabs added for readability): optionidproductidskunameitems 11123MW->123LW->123XLWSizes - ColorsM - White->L - White->XL -White0.00->0.00->1.00 They use the explode function to create a pulldown menu like this: Could a WebDNA function be written to split this single record into individual items? If so, any pointers would be helpful as I've written a function. On 5/9/06 11:21 AM, "Clint Davis" wrote: > I'm setting up a new store with some products requiring size/color options. > I noticed that StoreBuilder does this, but I don't like the implementation. > StoreBuilder assumes that every size is available in every color, but that's > not the case in my store. I may have red, blue, and green with sizes small, > medium, and large, but the red shirt is only available in small. > > I'll store options in a separate database, but I'm interested in how > everyone else handles this? ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Clint Davis
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...