Re: lazy programming
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 33818
interpreted = N
texte = >> You have to use the parameters in the replace tag to identify and>> retrieve only those records you need to replace, which means the>> category=Clothing&subcategory= belongs in the replace tag along>> with the blah=blah parameters, not inside the replace context. And>> of course this snippet of code has to be changed so it appears in the>> proper syntax, which means it has to look more like this:>> eqcategorydatarq=Clothing&eqsubcategorydatarq=[blank]>>hehe Right! this was lazy webcat list posting on my part :)>the actual replace context is:>[replace db=catalog.db&eqskudatarq=[sku]]>then the category is being generated with a formvariables, and so there will>always be a category=[value] inside the replace context. But I want to add>one at the end that in effect overides the one in the formvariables if it>exists. so the result inside the replace looks like [replace>db=catalog.db&eqskudatarq=[sku]]category=origvalue&category=newvalue[/replac>e] and I don't understand why it's not just replacing it twice cus it seems>like it shouldWebCat will never replace a field value twice because it only sees the *first* occurrence of the category value. If you want to replace the existing value with the non-formvariable value, you have to put that value FIRST, not second.================================Kenneth Grome, WebDNA Consultant808-737-6499 http://webdna.net================================-------------------------------------------------------------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://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
>> You have to use the parameters in the replace tag to identify and>> retrieve only those records you need to replace, which means the>> category=Clothing&subcategory= belongs in the replace tag along>> with the blah=blah parameters, not inside the replace context. And>> of course this snippet of code has to be changed so it appears in the>> proper syntax, which means it has to look more like this:>> eqcategorydatarq=Clothing&eqsubcategorydatarq=[blank]>>hehe Right! this was lazy webcat list posting on my part :)>the actual replace context is:>[replace db=catalog.db&eqskudatarq=[sku]]>then the category is being generated with a formvariables, and so there will>always be a category=[value] inside the replace context. But I want to add>one at the end that in effect overides the one in the formvariables if it>exists. so the result inside the replace looks like [replace>db=catalog.db&eqskudatarq=[sku]]category=origvalue&category=newvalue[/replac>e] and I don't understand why it's not just replacing it twice cus it seems>like it shouldWebCat will never replace a field value twice because it only sees the *first* occurrence of the category value. If you want to replace the existing value with the non-formvariable value, you have to put that value FIRST, not second.================================Kenneth Grome, WebDNA Consultant808-737-6499 http://webdna.net================================-------------------------------------------------------------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://search.smithmicro.com/
Kenneth Grome
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:
Funny Submissions From a Form Page (1999)
Word search (1997)
Semi OT: vbulletin and # viewing - how do that do that? (2003)
Who is doing sign-ups-got it (1998)
WebCatalog for Postcards ? (1997)
Redirect (2000)
Configuring E-mail (1997)
Sorting by date (1997)
Date Question (2002)
Date search - yes or no (1997)
NTbeta18 corrupted? (1997)
Help formatting search results w/ table (1997)
Thanks Grant (1997)
[Shownext] [whynot] (2000)
limitation found on group searching (1997)
Referrer field to header field conversion (1997)
[searchString] (1997)
Date problems-more (1997)
PCS Frames (1997)
Alternating colors (1997)