Re: Doesn't change (WebCat 4.0)

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 32869
interpreted = N
texte = Yes I agree, it's all hypothetical until we see the actual code in its entirety. But I don't think it's wasting everyone's time. After all, people can certainly learn from this important information, and then maybe they can resolve their own upgrade problems without needing to ask SM or anyone else how to fix it for them -- provided they know what to look for in the first place!Since this was the first problem I experienced with this version, I can only assume that it's going to be the first problem other people run into as well. That's one reason why I posted my 'theory'.I think that in Nitai's case, as well as in similar cases, if the action variable has not been preset, then it's probably a bug -- but if this variable was preset before the showif context, then changing the new preference ought to fix it instantly ... :) >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/================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================------------------------------------------------------------- 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:

    
  1. Re: Doesn't change (WebCat 4.0) (John Butler 2000)
  2. Re: Doesn't change (WebCat 4.0) (Paul Uttermohlen 2000)
  3. Re: Doesn't change (WebCat 4.0) (Kenneth Grome 2000)
  4. Re: Doesn't change (WebCat 4.0) (Jay Van Vark 2000)
  5. Re: Doesn't change (WebCat 4.0) (Kenneth Grome 2000)
  6. Re: Doesn't change (WebCat 4.0) (Jay Van Vark 2000)
  7. Re: Doesn't change (WebCat 4.0) (Kenneth Grome 2000)
  8. Re: Doesn't change (WebCat 4.0) (Jay Van Vark 2000)
  9. Doesn't change (WebCat 4.0) (Nitai @ Eyework 2000)
Yes I agree, it's all hypothetical until we see the actual code in its entirety. But I don't think it's wasting everyone's time. After all, people can certainly learn from this important information, and then maybe they can resolve their own upgrade problems without needing to ask SM or anyone else how to fix it for them -- provided they know what to look for in the first place!Since this was the first problem I experienced with this version, I can only assume that it's going to be the first problem other people run into as well. That's one reason why I posted my 'theory'.I think that in Nitai's case, as well as in similar cases, if the action variable has not been preset, then it's probably a bug -- but if this variable was preset before the showif context, then changing the new preference ought to fix it instantly ... :) >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/================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================------------------------------------------------------------- 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/ Kenneth Grome

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:

Mac & Internet Explorer (2000) [WebDNA] Help with work-around format date (2013) [taxrate] question (1997) Items in cart (2000) It finally happened ... (2003) [BULK] [WebDNA] Serial numbers and pricing for WebDNA 7.0 (2011) controlling form elements (slightly OT) (2003) webdna hideif / redirect - javascript disabled (2006) append=T problem (1998) Possible Bug 4.51 (2004) formula??? (2000) Loop into field (1998) [OT] Search Engine Tips (2003) New WebDNA Solutions ... (1997) docs for WebCatalog2 (1997) WebCatalog 4.0.1b1 is now available (2000) 2 Nt's (1998) CORR: date format (2000) Sorting Numbers (1997) Webcat causing crashes left and right! (1997)