numero = 20512
interpreted = N
texte = Hey there , I'm back..heh heh and the problem is not solved , I got a fewmore questions also, what in the Invoice template refersto numerically indexed names ? the only thing I could get out of it wasthat you meant the [Interpret] tags , but those are not specificon numerical or text characters , In deed I did not have to Interpret allof the fields but the wrong items where still displayed.and you asked about the {search][founditems] and sugested useing[formvaribles] , well that didnt work ethier , the search is used to find the neSKUdata and thus with the show if check[index] finding the multipleSKU's being sent in at one time , I tried adding and neSKUdata=[blank]into the formvaribles command but that made it go hay wire..heh heh and last on the Results Template how do you see [part#] and [category] andhaving numerical prefixes ?I appreciate the effort , but the problem still exists , anyone else got aclue ?ThanksChrisAt 11:15 AM 10/16/98, you wrote:>On 10/16/98 11:54 AM, Chris W. so noted...>>I think I've got a cold today, so I may not be the clearest, but this >jumped out at first glance.>>Your Invoice template refers to numerically indexed names for [check], >[part#] and [category] (also, why is [ModelDescription] being >[interpret]ed here?) ...>>>Invoice Template :>>>>[OrderFile cart=[cart]]>>>[Search db=[db]&neSKUdata=[blank]]>>[FoundItems]>>[ShowIf [Interpret][check[index]][/Interpret]=T]>>>>[AddLineItem db=[db]&cart=[cart]>>&sku=[sku]]part#=[Interpret][part#[index]][/Interpret]&Category=[Interpret][>>Category[index]][/Interpret]&ModelDescription=[Interpret]>>[ModelDescription][/Interpret][/AddLineItem]>>[/ShowIf]>>[/FoundItems]>>[/Search]>>But in the Results page, only [check] gets a numerical suffix. [part#] >and [category] do not ...>>>Results page :>>>[Search db=engine.txt&neSKUdata=[blank]&horsepowersort=1&cart=[cart]]>>[foundItems]>>>>
>>>>>>>>[/foundItems]>>[/Search]>>There may be other problems of a similar nature on the two pages as well, >but I think that this discrepancy between numbered and non-numbered >variables is at the root of your trouble.>>I should know better than to be posting : )>>>Rob Marquardt===================Part two. (see, *knew* I'd get into trouble! )Why are you doing a search on the Invoice Template to process the form? Instead of [search][founditems] shouldn't this be [formvariables]? Mixing commands and contexts always gets me confused -- even on a good day! ; )>Invoice Template : > >[OrderFile cart=[cart]] > > >[Search db=[db]&neSKUdata=[blank]] >[FoundItems] >[ShowIf [Interpret][check[index]][/Interpret]=T] > >[AddLineItem db=[db]&cart=[cart] >&sku=[sku]]part#=[Interpret][part#[index]][/Interpret]&Category=[Interpret][ >Category[index]][/Interpret]&ModelDescription=[Interpret] >[ModelDescription][/Interpret][/AddLineItem] >[/ShowIf] >[/FoundItems] >[/Search] >[include Fulfillment.txt] >[showif [email]!][include file=ThankYou.txt&v.email=[email]][/showif]Rob Marquardt=======================
Associated Messages, from the most recent to the oldest:
Hey there , I'm back..heh heh and the problem is not solved , I got a fewmore questions also, what in the Invoice template refersto numerically indexed names ? the only thing I could get out of it wasthat you meant the [interpret] tags , but those are not specificon numerical or text characters , In deed I did not have to Interpret allof the fields but the wrong items where still displayed.and you asked about the {search][founditems] and sugested useing[formvaribles] , well that didnt work ethier , the search is used to find the neSKUdata and thus with the show if check[index] finding the multipleSKU's being sent in at one time , I tried adding and neSKUdata=[blank]into the formvaribles command but that made it go hay wire..heh heh and last on the Results Template how do you see [part#] and [category] andhaving numerical prefixes ?I appreciate the effort , but the problem still exists , anyone else got aclue ?ThanksChrisAt 11:15 AM 10/16/98, you wrote:>On 10/16/98 11:54 AM, Chris W. so noted...>>I think I've got a cold today, so I may not be the clearest, but this >jumped out at first glance.>>Your Invoice template refers to numerically indexed names for [check], >[part#] and [category] (also, why is [ModelDescription] being >[interpret]ed here?) ...>>>Invoice Template :>>>>[OrderFile cart=[cart]]>>>[Search db=[db]&neSKUdata=[blank]]>>[founditems]>>[ShowIf [interpret][check[index]][/Interpret]=T]>>>>[AddLineItem db=[db]&cart=[cart]>>&sku=[sku]]part#=[interpret][part#[index]][/Interpret]&Category=[interpret][>>Category[index]][/Interpret]&ModelDescription=[interpret]>>[ModelDescription][/Interpret][/AddLineItem]>>[/ShowIf]>>[/FoundItems]>>[/Search]>>But in the Results page, only [check] gets a numerical suffix. [part#] >and [category] do not ...>>>Results page :>>>[Search db=engine.txt&neSKUdata=[blank]&horsepowersort=1&cart=[cart]]>>[founditems]>>>>
>>>>>>>>[/foundItems]>>[/Search]>>There may be other problems of a similar nature on the two pages as well, >but I think that this discrepancy between numbered and non-numbered >variables is at the root of your trouble.>>I should know better than to be posting : )>>>Rob Marquardt===================Part two. (see, *knew* I'd get into trouble! )Why are you doing a search on the Invoice Template to process the form? Instead of [search][founditems] shouldn't this be [formvariables]? Mixing commands and contexts always gets me confused -- even on a good day! ; )>Invoice Template : > >[OrderFile cart=[cart]] > > >[Search db=[db]&neSKUdata=[blank]] >[founditems] >[ShowIf [interpret][check[index]][/Interpret]=T] > >[AddLineItem db=[db]&cart=[cart] >&sku=[sku]]part#=[interpret][part#[index]][/Interpret]&Category=[interpret][ >Category[index]][/Interpret]&ModelDescription=[interpret] >[ModelDescription][/Interpret][/AddLineItem] >[/ShowIf] >[/FoundItems] >[/Search] >[include Fulfillment.txt] >[showif [email]!][include file=ThankYou.txt&v.email=[email]][/showif]Rob Marquardt=======================
Chris W.
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...