Re: color and size options

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 14638
interpreted = N
texte = >Go to http://search.smithmicro.com/mailinglists.html and search for product size in the subject line. On 10/22 you should see some ideas.Grant,Archives....what a wonderful thing!!!Below are the solutions you mentioned in the archive. I believe #2 will work for size, yet #3 (the database) will probably need to be used due to many different variations for color, for each garment. Could you possible give a brief example of how #3 would work. 2) There are just a few different lists of sizes Create SizePopup1.inc, SizePopup2.inc, SizePopup3.inc, each of which have the unique lists of sizes in them. Add a field to the database called [SizeType] that indicates which type of size poup it needs, 1, 2 or 3Then use [ShowIf [needsSize]=T][include SizePopup[SizeType].inc][/ShowIf] 3) There is a huge variety of size lists, basically unique to each product Either put the literal HTML for the whole popup into a field in the database, or create a related database (linked by SKU) that has all the size listings in it for each SKU. Thank you, Ray Hatch (trying to learn at the speed of an OC-12, comprehending at the speed of about 9600 baud...) Associated Messages, from the most recent to the oldest:

    
  1. Re: color and size options (Grant Hulbert 1997)
  2. Re: color and size options / ARCHIVES (Paul Uttermohlen 1997)
  3. Re: color and size options / ARCHIVES (Grant Hulbert 1997)
  4. Re: color and size options (Raymond Hatch 1997)
  5. Re: color and size options (Grant Hulbert 1997)
  6. color and size options (Raymond Hatch 1997)
>Go to http://search.smithmicro.com/mailinglists.html and search for product size in the subject line. On 10/22 you should see some ideas.Grant,Archives....what a wonderful thing!!!Below are the solutions you mentioned in the archive. I believe #2 will work for size, yet #3 (the database) will probably need to be used due to many different variations for color, for each garment. Could you possible give a brief example of how #3 would work. 2) There are just a few different lists of sizes Create SizePopup1.inc, SizePopup2.inc, SizePopup3.inc, each of which have the unique lists of sizes in them. Add a field to the database called [SizeType] that indicates which type of size poup it needs, 1, 2 or 3Then use [ShowIf [needsSize]=T][include SizePopup[SizeType].inc][/ShowIf] 3) There is a huge variety of size lists, basically unique to each product Either put the literal HTML for the whole popup into a field in the database, or create a related database (linked by SKU) that has all the size listings in it for each SKU. Thank you, Ray Hatch (trying to learn at the speed of an OC-12, comprehending at the speed of about 9600 baud...) Raymond Hatch

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

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...

Related Readings:

Capitalize special cases (2000) WebCatalog NT beta 18 now available (1997) This list needs a digest: rant, rave... (1997) bug in [SendMail] (1997) Multiple prices (1997) Enhancement Request for WebCatalog-NT (1996) listing [text] variables? (1999) [shippingtotal] in Formulas.db (2002) Looking for Experienced WebDNA Developer (2006) Running _every_ page through WebCat ? (1997) WebDNA tags in WebMerchant email templates ... (1997) OT: anyone know how to prevent image hijacking with Apache? (2002) Serial Number Question (1997) Stinkin' [Referrer] (1998) [WebDNA] Calculate Cube root (2012) Re[3]: Support suggestions - long (was politeness, et al) (2000) WebDNA 5.x Deployment? (2003) Using [showif] (2000) Follow-up to listfiles bug report ... (2003) [browsername] (2001)