Re: hideif/showif causes error if wrapped around searches
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 52874
interpreted = N
texte = WebDNA is basically an recursive 'inside-out' contextual parser. When a token is determined to be the beginning of a WebDNA context, the parser collects the inner content, up to the closing tag, and parses that before completing the executing the 'containing' context function. So, in your example code, WebDNA encounters the [hideif] context, and in the case when [hidesearch] is not 'T', the engine collects the inner content between the [hideif] tokens and attempts to parse it. But this fails because: "[search db=...] [founditems]" is incomplete, missing both the [/founditems] and [/search]. It's best to keep in mind that WebDNA code, existing between a context pair, needs to be syntactically complete. -----Original Message----- From: Gary Krockover [mailto:gary@garykrockover.com] Sent: Friday, September 12, 2003 9:20 PM To: WebDNA-Talk@talk.smithmicro.com Subject: hideif/showif causes error if wrapped around searches I know I'll never find this answer in the archives and I don't recall it even coming up before but I'm sure others have noticed this behavior. If you wrap a hideif or a showif around a [search] and it's closing [/search], you'll get an error about the nesting of the tags hideif/showif and /search. Por que? Example: [hideif [hidesearch]=T] (and it does) [search db=...] [founditems] [/hideif] Something else [hideif [hidesearch]=T] [/founditems] [/search] [/hideif] What am I trying to do? Add a sort for a page without having to make two pages with different searches on each. So a form post, with the search and a hidden field of hidesearch=T. The page is the home page, so when it is first hit I want the search performed automatically and sorted one way, user can click a button to sort it the other way, hiding the original search and using the one in the form. What's the preferred method here? Thanks, GK ------------------------------------------------------------- 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://webdna.smithmicro.com/ ------------------------------------------------------------- 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://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
WebDNA is basically an recursive 'inside-out' contextual parser. When a token is determined to be the beginning of a WebDNA context, the parser collects the inner content, up to the closing tag, and parses that before completing the executing the 'containing' context function. So, in your example code, WebDNA encounters the [hideif] context, and in the case when [hidesearch] is not 'T', the engine collects the inner content between the [hideif] tokens and attempts to parse it. But this fails because: "[search db=...] [founditems]" is incomplete, missing both the [/founditems] and [/search]. It's best to keep in mind that WebDNA code, existing between a context pair, needs to be syntactically complete. -----Original Message----- From: Gary Krockover [mailto:gary@garykrockover.com] Sent: Friday, September 12, 2003 9:20 PM To: WebDNA-Talk@talk.smithmicro.com Subject: hideif/showif causes error if wrapped around searches I know I'll never find this answer in the archives and I don't recall it even coming up before but I'm sure others have noticed this behavior. If you wrap a hideif or a showif around a [search] and it's closing [/search], you'll get an error about the nesting of the tags hideif/showif and /search. Por que? Example: [hideif [hidesearch]=T] (and it does) [search db=...] [founditems] [/hideif] Something else [hideif [hidesearch]=T] [/founditems] [/search] [/hideif] What am I trying to do? Add a sort for a page without having to make two pages with different searches on each. So a form post, with the search and a hidden field of hidesearch=T. The page is the home page, so when it is first hit I want the search performed automatically and sorted one way, user can click a button to sort it the other way, hiding the original search and using the one in the form. What's the preferred method here? Thanks, GK ------------------------------------------------------------- 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://webdna.smithmicro.com/ ------------------------------------------------------------- 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://webdna.smithmicro.com/
"Scott Anderson"
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:
taxTotal, too (1997)
SKU lookup (1997)
[protect admin] (1997)
WC2f3 (1997)
pictures / referrer etc. (1998)
How to find duplicates - With code samples (2000)
[WebDNA] proxy server domains mysteriously appear in webdna's domain list (2010)
WC Database Format (1997)
Shopping problems with 2.1b3 acgi (1997)
[SearchString] problem with [search] context (1997)
Deleting Orders (1997)
NEW NetProfessional Revealed (1998)
WebCat2b13 Mac plugin - [sendmail] and checkboxes (1997)
Searchable mail archive problems (2003)
How long until WebDNA makes the list? :( (2004)
Am I going senile? (Price recalc based on quantity) (1997)
Inventory lookup & display... (2003)
WCf2 and nested tags (1997)
Logging purchases (1997)
Intermitent problem using [referrer] (1997)