Re: [WebDNA] Variable mystery
This WebDNA talk-list message is from 2009
It keeps the original formatting.
numero = 102644
interpreted = N
texte = Terry Wilson wrote: > Maybe there's a typo, such as in your fieldname. Donovan Brooke wrote: > make sure the value of [PAGEKW] is not: ... Those were the very first things I checked. There were no typos anywhere. Donovan Brooke also wrote: > What version/platform of WebDNA are you using? CenOS 5 and the previous version of WebDNA. I know that's not a supported combo but this is not a complaint about WebDNA I'm just wondering how it can be possible with *any* OS and software. One possible explanation I thought of later is that I was working, ftp'ing updates, through the server's daily reboot. Could that be the reason? Govinda wrote: > Not that you have time or desire, but can you recreate the behavior > and show us in way that we could confirm on our own systems? I'll see what I can do. I'm a bit busy with a complete site overhaul right now. I've already moved on several steps from this incident so I can't just go back. I need to create a special demo page for it and I don't really have time for that today. I'll see what I can do later this week. --- But at least I can give a more detailed description if anybody are interested. The [PAGEKW] variable is used for an ads rototor, determining which advertisements are relevant for a specific page. Usually this is a fixed keyword (or set of keywords) for each page but on search result pages it needs to be set according to the search phrase. So I have a database that looks something like this: pgUrl pgPakeKw someotherpage.html relevantkeyword searchresults.html [PHRASE] Then I define [PAGEKW] early in the template: [TEXT]PAGEKW=[pgPageKw][/TEXT] This of course works well when [pgPageKw] is a fixed string. On someotherpage.html the [PAGEKW] tag is replaced by relevantkeyword. It shouldn't have worked at all when [pgPageKw] was a tag but somehow it kind'a half worked. On searchresults.html?phrase=flute [PAGEKW] displayed as flute when placed on the page on its own but was kept as raw [PAGEKW] when nested inside another WebDNA tag. The *correct* way to set the value would of course be: [TEXT]PAGEKW=[INTERPRET][pgPageKw][/INTERPRET][/TEXT] and that works just fine. Case solved but the mystery still remains. Frank Nordberg http://www.musicaviva.com
Associated Messages, from the most recent to the oldest:
Terry Wilson wrote: > Maybe there's a typo, such as in your fieldname. Donovan Brooke wrote: > make sure the value of [PAGEKW] is not: ... Those were the very first things I checked. There were no typos anywhere. Donovan Brooke also wrote: > What version/platform of WebDNA are you using? CenOS 5 and the previous version of WebDNA. I know that's not a supported combo but this is not a complaint about WebDNA I'm just wondering how it can be possible with *any* OS and software. One possible explanation I thought of later is that I was working, ftp'ing updates, through the server's daily reboot. Could that be the reason? Govinda wrote: > Not that you have time or desire, but can you recreate the behavior > and show us in way that we could confirm on our own systems? I'll see what I can do. I'm a bit busy with a complete site overhaul right now. I've already moved on several steps from this incident so I can't just go back. I need to create a special demo page for it and I don't really have time for that today. I'll see what I can do later this week. --- But at least I can give a more detailed description if anybody are interested. The [PAGEKW] variable is used for an ads rototor, determining which advertisements are relevant for a specific page. Usually this is a fixed keyword (or set of keywords) for each page but on search result pages it needs to be set according to the search phrase. So I have a database that looks something like this: pgUrl pgPakeKw someotherpage.html relevantkeyword searchresults.html [PHRASE] Then I define [PAGEKW] early in the template:
[text]PAGEKW=[pgPageKw][/TEXT] This of course works well when [pgPageKw] is a fixed string. On someotherpage.html the [PAGEKW] tag is replaced by relevantkeyword. It shouldn't have worked at all when [pgPageKw] was a tag but somehow it kind'a half worked. On searchresults.html?phrase=flute [PAGEKW] displayed as flute when placed on the page on its own but was kept as raw [PAGEKW] when nested inside another WebDNA tag. The *correct* way to set the value would of course be:
[text]PAGEKW=
[interpret][pgPageKw][/INTERPRET][/TEXT] and that works just fine. Case solved but the mystery still remains. Frank Nordberg http://www.musicaviva.com
Frank Nordberg
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:
Drop Down Menus (2002)
[dos] command and [math] (1998)
RE: HTTP Header info (1997)
Closing db's & caching templates (was: Shippingcalculations) (1997)
suffix mapping for NT? (1997)
Ok here is a question? (1997)
More on the email templates (1997)
WebCat Error Log problem (2.0.1, acgi, Mac) (1997)
Passing radio check box value to itself... (2000)
Browser Problem?!? POST forms and NN 4.0+ browsers (1997)
[WebDNA] Interesting Trigger issue (2020)
Include a big block of text (1997)
fixed date problem (1997)
Webcat run amuk (2002)
random images (1997)
Calendar (1997)
[Price] (1997)
UnitShopCost (2007)
Re[2]: Unix Webcat Permission - Suggestions (2000)
Other then credit cards-how? (1997)