Re: [WebDNA] Variable mystery
This WebDNA talk-list message is from 2009
It keeps the original formatting.
numero = 102652
interpreted = N
texte = Ken, you missed the earlier description of the problem wherein his variable literally contains the square-bracketed name of another variable, so yes the [interpret] was needed in this case. Brian Fries BrainScan Software On Jun 3, 2009, at 7:02 AM, Kenneth Grome wrote: >>> The interpret should not be required when that code is >>> inside a search context. >> >> It shouldn't? > > No of course not. Normally you need an interpret context > only when the tag or context would *not* be interpreted -- > but [variable] tags are always interpreted by default -- > unless something prevents it of course ... > > There is a preference settings that can affect [variable] > interpretation, but I don't think many people change, it so > this is probably not an issue for you anyways. > > It must be something you're doing in the code above that > search context that's preventing the tag from being > interpreted normally. > > >> The problem definitely went away when I added that >> interpet context and I didn't make any other changes at >> that point. > > I guess that's all that matters in the grand scheme of > things anyways ... :) > > Sincerely, > Ken Grome > > > > --------------------------------------------------------- > 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 > old archives: http://dev.webdna.us/TalkListArchive/
Associated Messages, from the most recent to the oldest:
Ken, you missed the earlier description of the problem wherein his variable literally contains the square-bracketed name of another variable, so yes the [interpret] was needed in this case. Brian Fries BrainScan Software On Jun 3, 2009, at 7:02 AM, Kenneth Grome wrote: >>> The interpret should not be required when that code is >>> inside a search context. >> >> It shouldn't? > > No of course not. Normally you need an interpret context > only when the tag or context would *not* be interpreted -- > but [variable] tags are always interpreted by default -- > unless something prevents it of course ... > > There is a preference settings that can affect [variable] > interpretation, but I don't think many people change, it so > this is probably not an issue for you anyways. > > It must be something you're doing in the code above that > search context that's preventing the tag from being > interpreted normally. > > >> The problem definitely went away when I added that >> interpet context and I didn't make any other changes at >> that point. > > I guess that's all that matters in the grand scheme of > things anyways ... :) > > Sincerely, > Ken Grome > > > > --------------------------------------------------------- > 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 > old archives: http://dev.webdna.us/TalkListArchive/
Brian Fries
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:
[WebDNA] Lookup inside grep?... (2011)
IIS error and webcat (2000)
Smart caching problems with 2.1b3? (1997)
Navigator 4.01 (1997)
Pithy questions on webcommerce & siteedit (1997)
Nested tags count question (1997)
auto adding SKUs w/DB helper (1998)
RequiredFields template (1997)
WebCat2b13 Mac plugin - [sendmail] and checkboxes (1997)
Where is f2? (1997)
Frames and WebCat (1997)
Search results templates (1996)
NT 4.0/IIS WebCat Installation (1998)
Large founditems loops (2000)
WebMerchant 1.6 and SHTML (1997)
[OT] Form POSTing with LONG variable (2007)
[Price] (1997)
Server capacity (2003)
Replace Statement (1997)
default value from Lookup (was Grant, please help me) (1997)