Re: WebDNA 6.0 backwards compatible?

This WebDNA talk-list message is from

2004


It keeps the original formatting.
numero = 57036
interpreted = N
texte = Upgrading from 3.0, you need to be aware of one particular change to the WebDNA engine (introduced with version 4). This has to do with the 'switch' in precedence between text or math variables, and incoming form variables. Prior to WebDNA version 4, incoming form variables would 'override' any text or math variables of the same name. Starting with version 4, the default behavior of the engine was changed so that incoming form variables would not take precedence over text and math variables. This was a necessary 'security' improvement. However, it did require some WebDNA programmers to make changes to their existing templates. If much of your WebDNA code relies on the 'old' engine behavior, there is a way to get a newer WebDNA version to run in pre 4.0 mode. Simply set the WebDNA 'InsecureTextVars' pref to '1', and newer WebDNA versions will revert to the original method of resolving form varibales, ahead of text variables. I do not recommend doing this, however. Instead, I would just make the necessary code changes. For example: If you are used to setting default values for text variables, anticipating that incomming fcrm variables will 'replace' the default values, you can make the following change: [Text]Var1=some_default_value[/Text] becomes [Text secure=F]Var1=some+default_value[/Text] In this case, [Var1] will resolve to the default value, unless a formvariable, also named 'Var1' has been passed to the template. -----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of Alisha Outridge Sent: Sunday, March 21, 2004 1:31 PM To: WebDNA Talk Subject: WebDNA 6.0 backwards compatible? Is WebDNA 6.0 backwards-compatible with WebCat 3.0? We're looking to upgrade with as little issues as possible... ------------------------------------------------------------- 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:

    
  1. Re: WebDNA 6.0 backwards compatible? ( "Scott Anderson" 2004)
  2. Re: WebDNA 6.0 backwards compatible? ( Alisha Outridge 2004)
  3. Re: WebDNA 6.0 backwards compatible? ( Alisha Outridge 2004)
  4. Re: WebDNA 6.0 backwards compatible? ( Donovan Brooke 2004)
  5. Re: WebDNA 6.0 backwards compatible? ( Terry Wilson 2004)
  6. Re: WebDNA 6.0 backwards compatible? ( "Scott Anderson" 2004)
  7. Re: WebDNA 6.0 backwards compatible? ( Daryl Mitchell 2004)
  8. Re: WebDNA 6.0 backwards compatible? ( Donovan Brooke 2004)
  9. WebDNA 6.0 backwards compatible? ( Alisha Outridge 2004)
Upgrading from 3.0, you need to be aware of one particular change to the WebDNA engine (introduced with version 4). This has to do with the 'switch' in precedence between text or math variables, and incoming form variables. Prior to WebDNA version 4, incoming form variables would 'override' any text or math variables of the same name. Starting with version 4, the default behavior of the engine was changed so that incoming form variables would not take precedence over text and math variables. This was a necessary 'security' improvement. However, it did require some WebDNA programmers to make changes to their existing templates. If much of your WebDNA code relies on the 'old' engine behavior, there is a way to get a newer WebDNA version to run in pre 4.0 mode. Simply set the WebDNA 'InsecureTextVars' pref to '1', and newer WebDNA versions will revert to the original method of resolving form varibales, ahead of text variables. I do not recommend doing this, however. Instead, I would just make the necessary code changes. For example: If you are used to setting default values for text variables, anticipating that incomming fcrm variables will 'replace' the default values, you can make the following change: [text]Var1=some_default_value[/Text] becomes [Text secure=F]Var1=some+default_value[/Text] In this case, [Var1] will resolve to the default value, unless a formvariable, also named 'Var1' has been passed to the template. -----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of Alisha Outridge Sent: Sunday, March 21, 2004 1:31 PM To: WebDNA Talk Subject: WebDNA 6.0 backwards compatible? Is WebDNA 6.0 backwards-compatible with WebCat 3.0? We're looking to upgrade with as little issues as possible... ------------------------------------------------------------- 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:

[protect admin] (1997) emailer (1997) 2.0Beta Command Ref (can't find this instruction) (1997) extending webcatalog (1997) find with exceptions (1997) NewCart+Search with one click ? (1997) [ConvertChars] problem (1997) WebCat2 Append problem (B14Macacgi) (1997) Nested search (1997) Math Help (2000) WebCat2: Items xx to xx shown, etc. (1997) Thanks ! (1997) Memory Error message (1998) Add - optional parameters textA=.... (1997) Harvesting invalid email addresses from bounced emails??? (2000) Re:Emailer and encryption (1997) [WebDNA] centos 5.2 which is better 32bit or 64 bit (2009) Documentation Feedback (1997) Limiting user access to .tmpl files (1997) [include] affect on filepaths for links? (1997)