Re: using [URL] in search parameters?
This WebDNA talk-list message is from 1999
It keeps the original formatting.
numero = 25572
interpreted = N
texte = >In this replace context->[Replace db=Subscribers.db&eqEmaildatarq=[EmailAddress]&append=T]>should [EmailAddress] be wrapped in an [URL] context?It may not be absolutely necessary in this case -- assuming the value of [EmailAddress] is actually valid email address, because email addresses cannot legally contain = or & characters -- but it's still a good practice to get into.Let's say you were asking about [companyName] instead of [EmailAddress], and the value of [companyName] were something like Jane & Bob's Grille for example. Then yes, of course you would have to [url] the [companyName] tag -- because it contains the & character, which is not supposed to appear in the search string anywhere *except* in between name=value parameter pairs.It's a simple concept really:The = sign is always assumed to connect a name to a value, and the & character is always assumed to separate one name=value pair from another.So when you [url] a tag, you automatically change any = signs to %3D, and & characters are changed to %26, thus prevent them from appearing as = and &. And that prevents them from breaking the search string ...================================Kenneth Grome, WebDNA Consultant808-737-6499, http://webdna.net================================-------------------------------------------------------------Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server.To end your Mail problems go to
.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
Associated Messages, from the most recent to the oldest:
>In this replace context->[Replace db=Subscribers.db&eqEmaildatarq=[EmailAddress]&append=T]>should [EmailAddress] be wrapped in an [url] context?It may not be absolutely necessary in this case -- assuming the value of [EmailAddress] is actually valid email address, because email addresses cannot legally contain = or & characters -- but it's still a good practice to get into.Let's say you were asking about [companyName] instead of [EmailAddress], and the value of [companyName] were something like Jane & Bob's Grille for example. Then yes, of course you would have to [url] the [companyName] tag -- because it contains the & character, which is not supposed to appear in the search string anywhere *except* in between name=value parameter pairs.It's a simple concept really:The = sign is always assumed to connect a name to a value, and the & character is always assumed to separate one name=value pair from another.So when you [url] a tag, you automatically change any = signs to %3D, and & characters are changed to %26, thus prevent them from appearing as = and &. And that prevents them from breaking the search string ...================================Kenneth Grome, WebDNA Consultant808-737-6499, http://webdna.net================================-------------------------------------------------------------Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server.To end your Mail problems go to .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
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:
Signal Raised (1997)
Transferring [cart] to Database (1997)
oops private message leaked into talk list (1997)
Signal Raised Error (Part II) (1997)
Calculating multiple shipping... (1997)
5.0 Pricing (2003)
removelineitems (2000)
Which beta for w* 4.1 and a problem w/b12 (1999)
PCS Frames (1997)
Multiple prices (1997)
[BULK] [WebDNA] [BULK] WebDNA 7 - Ready or Not ?? I'm not sure... (2011)
Interpret twice? (1997)
Variables for chat (1997)
php vs WebCatalog (2000)
For those of you not on the WebCatalog Beta... (1997)
[no_cache]?! (2000)
b12 cannot limit records returned and more. (1997)
Normalizing Dates and Phone numbers (2000)
flushing databases (2003)
Merging databases (1997)