Re: Doesn't change (WebCat 4.0)
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 32864
interpreted = N
texte = Agreed with your hypothetical, but since we don't have all the facts we are both just guessing... and wasting everyones time...>Jay, this example clearly illustrates one of the *first* problems I >discovered with the new 4.0 variable hierarchy whenever someone >declares a page variable value before that variable is used in a >showif context. > >If in fact Nitai has set her action variable to any value other >than save1 before her showif context, then this directly applies to >Nitai's problem. Heres how it works: > >If Nitai used this code (or something like it) anywhere in the page >*before* her showif context: > >[text]action=[/text] > >... then the value of the incoming formvariable named save1 will be >overridden by the 'blank' value set in the text context. This will >cause the showif to hide the enclosed code -- which is the exact >*opposite* of the default behavior in version 3.x. > >This is why I *specifically* asked Nitai whether or not she had >declared the value of action as a text variable. You may not know >it, but it is a very common practice for webdna coding professionals >to set their text variables to blank values at the top of the page, >because doing so allows us to use simple showif comparisons like this: > >[showif [var1]=] > >... instead of the more difficult and time-consuming: > >[showif [var1]=[raw][var1][/raw]] > >Therefore, anyone who has been pre-setting their text variables in >this manner is subject to having their code fail when they upgrade to >version 4 -- unless they perform one of the tasts I mentioned in my >previous message (still quoted below). > >If Nitai *has* declared a value for action anywhere in the page >before her showif context, then that is exactly what is causing this >template to fail on version 4. Of course, if that's not the >situation, then maybe she is running into the bug I found yesterday >-- which SM has not yet followed up on -- or maybe she has uncovered >another new bug. > >I am very curious about the facts of this situation. So far I have >not seen the webdna code in its entirety, so my theory is just that >-- a theory. > >Nitai, will you please post (or email me privately) the complete >katadd.tpl template? You can simply attach it to an email message >if you contact me privately. > >And if you post the complete page to this talk list, maybe one or >more of us can help you to find the problem. SM never found this >problem in their beta testing, or you wouldn't be dealing with it >now, would you? > >I think you might benefit from others on the list seeing what's >actually going on here. We are all here to support each other, so >just 'show us your code' and we will help as much as we can! > >:) > > > >>This has nothing to do with the variable hierarchy.... >> >>>Nitai, >>> >>>You don't have to go thru SM's tech support procedures to get this >>>problem resolved. This is a *perfect* example of how the new 4.0 >>>default variable hierarchy can break your existing templates ... >>> >>>You probably preset the value of the action variable to a blank >>>value at the top of the atadd.tpl page, didn't you? Lots of us have >>>adopted this coding technique during the past year or two to clean up >>>our code and to make our coding work easier ... >>> >>>Unfortunately, if you try to use the new default variable hierarchy, >>>this technique will no longer be possible -- because incoming >>>formvariables will never override the preset text variable values in >>>the new default hierarchy. >>> >>>Therefore, to make your site work the way it used to with version 3, >>>you must now: >>> >>>1- Get rid of all your preset text and math variable values *and* >>>change all your showif's and hideif's that compare like this: [showif >>>[var1]=] to this kind of comparison instead: [showif >>>[var1]=[raw][var1][/raw]] >>> >>>OR you can ... >>> >>>2- Change all your [text] tags to [text secure=f] tags. >>> >>>OR you can ... >>> >>>3- Change the insecureTextVars preference from 0 to 1. >>> >>> >>>Obviously #3 is the easiest ... :) >>> >>>>Please coordinate this directly through webcatalog@smithmicro.com so >>>>that we can track this down quickly... >>>> >>>>Make sure to include specifics about what doesn't work -- what is it doing? >>>> >>>>Thanks! >>>> >>>>>Now, I don't know if this is the text thing we have talked about >>>>>it but lets >>>>>see: >>>>> >>>>>I have this form> >>>>> >>>>>
>>>>> >>>>>And on katadd.tpl this: >>>>> >>>>>[showif [action]=save1] >>>>> >>>>>[search >>>>>db=../data/kat.db&gekatiddata=0&katidtype=numm&dekatidsort=1&max=1] >>>>>[math show=f]newnummer=[founditems][katid][/founditems]+1[/math] >>>>>[/search] >>>>> >>>>>[append >>>>>db=../data/kat.db]katid=[newnummer]&kat1=[url][__kat1][/url][/append] >>>>> >>>>>[/showif] >>>>> >>>>>Now with WebCat 3.x this works fine, but with WebCat 4.0 it doesn't. Any >>>>>clues? >>>>> >>>>>TIA. >>>>>Sincerely, >>>>>Nitai >>>>> >>>>>-- >>>>>Ecommerce für Ihre Ziele >>>>>Eyework - http://eyework.net/ >>>>> >>>>>EMail: Info@eyework.net >>>>>Tel: +41 (0)52 / 654 15 55, Fax: +41 (0)52 / 654 15 59 >>>>>Jay Van Vark *********************************** Smith Micro, Internet Solutions Div | eCommerce (WebCatalog) 16855 West Bernardo Drive | Software & Site Development Suite 380 | http://www.smithmicro.com/isd San Diego, CA 92127 | ------------------------- 858.675.1106 | Wireless WebDNA 858.675.0372 (fax) ***********************************NASDQ: SMSI ------------------------------------------------------------- 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://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Agreed with your hypothetical, but since we don't have all the facts we are both just guessing... and wasting everyones time...>Jay, this example clearly illustrates one of the *first* problems I >discovered with the new 4.0 variable hierarchy whenever someone >declares a page variable value before that variable is used in a >showif context. > >If in fact Nitai has set her action variable to any value other >than save1 before her showif context, then this directly applies to >Nitai's problem. Heres how it works: > >If Nitai used this code (or something like it) anywhere in the page >*before* her showif context: > >[text]action=[/text] > >... then the value of the incoming formvariable named save1 will be >overridden by the 'blank' value set in the text context. This will >cause the showif to hide the enclosed code -- which is the exact >*opposite* of the default behavior in version 3.x. > >This is why I *specifically* asked Nitai whether or not she had >declared the value of action as a text variable. You may not know >it, but it is a very common practice for webdna coding professionals >to set their text variables to blank values at the top of the page, >because doing so allows us to use simple showif comparisons like this: > >[showif [var1]=] > >... instead of the more difficult and time-consuming: > >[showif [var1]=[raw][var1][/raw]] > >Therefore, anyone who has been pre-setting their text variables in >this manner is subject to having their code fail when they upgrade to >version 4 -- unless they perform one of the tasts I mentioned in my >previous message (still quoted below). > >If Nitai *has* declared a value for action anywhere in the page >before her showif context, then that is exactly what is causing this >template to fail on version 4. Of course, if that's not the >situation, then maybe she is running into the bug I found yesterday >-- which SM has not yet followed up on -- or maybe she has uncovered >another new bug. > >I am very curious about the facts of this situation. So far I have >not seen the webdna code in its entirety, so my theory is just that >-- a theory. > >Nitai, will you please post (or email me privately) the complete >katadd.tpl template? You can simply attach it to an email message >if you contact me privately. > >And if you post the complete page to this Talk List, maybe one or >more of us can help you to find the problem. SM never found this >problem in their beta testing, or you wouldn't be dealing with it >now, would you? > >I think you might benefit from others on the list seeing what's >actually going on here. We are all here to support each other, so >just 'show us your code' and we will help as much as we can! > >:) > > > >>This has nothing to do with the variable hierarchy.... >> >>>Nitai, >>> >>>You don't have to go thru SM's tech support procedures to get this >>>problem resolved. This is a *perfect* example of how the new 4.0 >>>default variable hierarchy can break your existing templates ... >>> >>>You probably preset the value of the action variable to a blank >>>value at the top of the atadd.tpl page, didn't you? Lots of us have >>>adopted this coding technique during the past year or two to clean up >>>our code and to make our coding work easier ... >>> >>>Unfortunately, if you try to use the new default variable hierarchy, >>>this technique will no longer be possible -- because incoming >>>formvariables will never override the preset text variable values in >>>the new default hierarchy. >>> >>>Therefore, to make your site work the way it used to with version 3, >>>you must now: >>> >>>1- Get rid of all your preset text and math variable values *and* >>>change all your showif's and hideif's that compare like this: [showif >>>[var1]=] to this kind of comparison instead: [showif >>>[var1]=[raw][var1][/raw]] >>> >>>OR you can ... >>> >>>2- Change all your [text] tags to [text secure=f] tags. >>> >>>OR you can ... >>> >>>3- Change the insecureTextVars preference from 0 to 1. >>> >>> >>>Obviously #3 is the easiest ... :) >>> >>>>Please coordinate this directly through webcatalog@smithmicro.com so >>>>that we can track this down quickly... >>>> >>>>Make sure to include specifics about what doesn't work -- what is it doing? >>>> >>>>Thanks! >>>> >>>>>Now, I don't know if this is the text thing we have talked about >>>>>it but lets >>>>>see: >>>>> >>>>>I have this form> >>>>> >>>>> >>>>> >>>>>And on katadd.tpl this: >>>>> >>>>>[showif [action]=save1] >>>>> >>>>>[search >>>>>db=../data/kat.db&gekatiddata=0&katidtype=numm&dekatidsort=1&max=1] >>>>>[math show=f]newnummer=[founditems][katid][/founditems]+1[/math] >>>>>[/search] >>>>> >>>>>[append >>>>>db=../data/kat.db]katid=[newnummer]&kat1=[url][__kat1][/url][/append] >>>>> >>>>>[/showif] >>>>> >>>>>Now with WebCat 3.x this works fine, but with WebCat 4.0 it doesn't. Any >>>>>clues? >>>>> >>>>>TIA. >>>>>Sincerely, >>>>>Nitai >>>>> >>>>>-- >>>>>Ecommerce für Ihre Ziele >>>>>Eyework - http://eyework.net/ >>>>> >>>>>EMail: Info@eyework.net >>>>>Tel: +41 (0)52 / 654 15 55, Fax: +41 (0)52 / 654 15 59 >>>>>Jay Van Vark *********************************** Smith Micro, Internet Solutions Div | eCommerce (WebCatalog) 16855 West Bernardo Drive | Software & Site Development Suite 380 | http://www.smithmicro.com/isd San Diego, CA 92127 | ------------------------- 858.675.1106 | Wireless WebDNA 858.675.0372 (fax) ***********************************NASDQ: SMSI ------------------------------------------------------------- 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://search.smithmicro.com/
Jay Van Vark
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:
Comments in db? (1997)
$Quit, $CloseDatabase corrections (1997)
Proposed FormVariables hierarchy (2000)
Line Endings (2003)
WebCat2 - Getting to the browser's username/password data (1997)
WebCat2: Items xx to xx shown, etc. (1997)
Sendmail Question (2001)
PCS Frames (1997)
Sendmail double space (2001)
[shownext] support - MacOS (1997)
Almost a there but..bye bye NetCloak (1997)
carriage returns in data (1997)
WebCatalog Eating 200% of the CPU (2002)
Press Release hit the NewsWire!!! (1997)
WebCatalog NT beta 18 problem (1997)
WebCat2 - Getting to the browser's username/password data (1997)
UPS Rates (2006)
email bounce check (2002)
Sendmail - Attachment / My First Post (2001)
WebCommerce: Folder organization ? (1997)