Re: [WebDNA] [redirect] include a value to pass along?
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 105687
interpreted = N
texte = This is a multi-part message in MIME format. --------------060203050109010105050203 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi Govinda, I do use [url] on all my form variables, appends, replacements and other places. I didn't feel it necessary to use it in this particluar redirect as the variables had no chance of containing illegals. Thanks for taking the time to explain this. Steve Govinda wrote: > Steve, > you are all set, so I don't need to say anything more here really.. > but just a side note: > > One thing that factors in to the overall understanding here is that > the [url] context is useful (if not downright required when you have > dynamic vals coming in via variables - for webdna context param vals) > for not only preventing URLs and comparisons (like [showif...]) from > breaking/failing, but also useful *anytime* you are not sure if the > chars that end up in a webdna context *parameter* ("param") value > might break that param's value. Like the "&" char delimits one param > from another .. in webdna as well as in URLs.. so you can wrap the > param value with [url]...[/url]. > > The background on why [redirect] has those 2 formats/methods that you > saw here today is that in the old days [redirect myPage.html] was good > enough. But later they wanted *every* param to be defined by a > name/value pair (not just a value sometimes).. so that it was > consistent with what used to be called webdna's "XML syntax" - > something that has been dropped in the meanwhile. The bit after > "[redirect" is the page you want to redirect to. But that is actually > [redirect]'s *param* value.. and so in the XML syntax style needed to > be named. Just like [formvariables] has a "name" param.. and an > "exact" param.. so like that [redirect] has the "url" *parameter*. > > Again this is just some background; the methods the others already > showed you today keep your (http) URL params from breaking inside your > [redirect].. I just wanted to point out why different methods evolved. > > ------------ > Govinda > govinda.webdnatalk@gmail.com > > > > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list
. > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us > --------------060203050109010105050203 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi Govinda,
I do use [url] on all my form variables, appends, replacements and other places. I didn't feel it necessary to use it in this particluar redirect as the variables had no chance of containing illegals. Thanks for taking the time to explain this.
Steve
Govinda wrote: Steve,
you are all set, so I don't need to say anything more here really.. but just a side note:
One thing that factors in to the overall understanding here is that the [url] context is useful (if not downright required when you have dynamic vals coming in via variables - for webdna context param vals) for not only preventing URLs and comparisons (like [showif...]) from breaking/failing, but also useful *anytime* you are not sure if the chars that end up in a webdna context *parameter* ("param") value might break that param's value. Like the "&" char delimits one param from another .. in webdna as well as in URLs.. so you can wrap the param value with [url]...[/url].
The background on why [redirect] has those 2 formats/methods that you saw here today is that in the old days [redirect myPage.html] was good enough. But later they wanted *every* param to be defined by a name/value pair (not just a value sometimes).. so that it was consistent with what used to be called webdna's "XML syntax" - something that has been dropped in the meanwhile. The bit after "[redirect" is the page you want to redirect to. But that is actually [redirect]'s *param* value.. and so in the XML syntax style needed to be named. Just like [formvariables] has a "name" param.. and an "exact" param.. so like that [redirect] has the "url" *parameter*.
Again this is just some background; the methods the others already showed you today keep your (http) URL params from breaking inside your [redirect].. I just wanted to point out why different methods evolved.
------------
Govinda
govinda.webdnatalk@gmail.com
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us
--------------060203050109010105050203--
Associated Messages, from the most recent to the oldest:
This is a multi-part message in MIME format. --------------060203050109010105050203 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi Govinda, I do use [url] on all my form variables, appends, replacements and other places. I didn't feel it necessary to use it in this particluar redirect as the variables had no chance of containing illegals. Thanks for taking the time to explain this. Steve Govinda wrote: > Steve, > you are all set, so I don't need to say anything more here really.. > but just a side note: > > One thing that factors in to the overall understanding here is that > the [url] context is useful (if not downright required when you have > dynamic vals coming in via variables - for webdna context param vals) > for not only preventing URLs and comparisons (like [showif...]) from > breaking/failing, but also useful *anytime* you are not sure if the > chars that end up in a webdna context *parameter* ("param") value > might break that param's value. Like the "&" char delimits one param > from another .. in webdna as well as in URLs.. so you can wrap the > param value with [url]...[/url]. > > The background on why [redirect] has those 2 formats/methods that you > saw here today is that in the old days [redirect myPage.html] was good > enough. But later they wanted *every* param to be defined by a > name/value pair (not just a value sometimes).. so that it was > consistent with what used to be called webdna's "XML syntax" - > something that has been dropped in the meanwhile. The bit after > "[redirect" is the page you want to redirect to. But that is actually > [redirect]'s *param* value.. and so in the XML syntax style needed to > be named. Just like [formvariables] has a "name" param.. and an > "exact" param.. so like that [redirect] has the "url" *parameter*. > > Again this is just some background; the methods the others already > showed you today keep your (http) URL params from breaking inside your > [redirect].. I just wanted to point out why different methods evolved. > > ------------ > Govinda > govinda.webdnatalk@gmail.com > > > > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us > --------------060203050109010105050203 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi Govinda,
I do use [url] on all my form variables, appends, replacements and other places. I didn't feel it necessary to use it in this particluar redirect as the variables had no chance of containing illegals. Thanks for taking the time to explain this.
Steve
Govinda wrote: Steve,
you are all set, so I don't need to say anything more here really.. but just a side note:
One thing that factors in to the overall understanding here is that the [url] context is useful (if not downright required when you have dynamic vals coming in via variables - for webdna context param vals) for not only preventing URLs and comparisons (like [showif...]) from breaking/failing, but also useful *anytime* you are not sure if the chars that end up in a webdna context *parameter* ("param") value might break that param's value. Like the "&" char delimits one param from another .. in webdna as well as in URLs.. so you can wrap the param value with [url]...[/url].
The background on why [redirect] has those 2 formats/methods that you saw here today is that in the old days [redirect myPage.html] was good enough. But later they wanted *every* param to be defined by a name/value pair (not just a value sometimes).. so that it was consistent with what used to be called webdna's "XML syntax" - something that has been dropped in the meanwhile. The bit after "[redirect" is the page you want to redirect to. But that is actually [redirect]'s *param* value.. and so in the XML syntax style needed to be named. Just like [formvariables] has a "name" param.. and an "exact" param.. so like that [redirect] has the "url" *parameter*.
Again this is just some background; the methods the others already showed you today keep your (http) URL params from breaking inside your [redirect].. I just wanted to point out why different methods evolved.
------------
Govinda
govinda.webdnatalk@gmail.com
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us
--------------060203050109010105050203--
Steve Raslevich
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:
E-mailer application times out (1998)
WCS Newbie question (1997)
[shownext max=?] armed (1997)
[UPPERCASE] (1997)
RE: Just a thought (1998)
NewCart+Search with one click ? (1997)
2 databases (1998)
Location of Browser Info.txt file (1997)
Help with [LineItems] in [OrderFile] on ShoppingCart.tpl (2003)
[WebDNA] WebDNA databases not showing? (2013)
Summing fields (1997)
RE: How to verify email address (1997)
WebMerchant 2.1.2 (1998)
[addlineitems] (1997)
Windows-based Code Editor (2002)
WebCatalog2 Feature Feedback (1996)
Nesting format tags (1997)
database size? (1997)
[ShowIf] if the varieable exists (1998)
LOG IN LOG OUT (1997)