Re: WebCatalog not running after upgrade
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 35175
interpreted = N
texte = >OK ignoring obvious errors in code like ending brackets etc which may >have worked with 3 but would now crash with 4 are there _any_ >'tags/contexts/coding techniques' that do not work the same as 3 - >even if they don't actually crash 4? Yes of course! In fact, there are at least two MAJOR issues:1- If your coding techniques have used form variables to override text variables, your old code will break. This coding technique was always the default before, but beginning with version 4 this has changed ...2- If your coding techniques have used a space character in field or variable names, your old code will break. The only solution is to recode your old sites to get rid of the spaces if you want them to work with version 4. By the way, before John Peacock jumps in here (again) and tries to make an issue out of the fact that it is stupid to use spaces in field and variable names, just let me say this once again, so everyone knows the TRUTH and the FACTS regarding the use of spaces in the webdna language:1- Spaces have *always* been acceptable field and variable name characters -- until version 4. This is a fact.2- Grant Hulbert, the webcatalog software engineer, specifically told me (years ago) that we *can* use space characters in field and variable names. He said he coded webcatalog *specifically* to deal with space characters in field and variable names exactly the same as any alphanumeric character would be dealt with in the same place.And he was right -- until version 4, that it.3- In other words, it has never been 'wrong', nor has it ever been 'stupid', to use spaces in field and variable names. After all, the webdna language was coded specifically to ALLOW us to use spaces in these places with no problem -- until version 4.4- It is only now, with the release of version 4, that SM has decided to eliminate space characters as acceptable field and variable name characters in webcatalog. This means if you have ever used spaces in these places previously, your old sites will fail unless you upgrade them to match the more limited capabilities of version 4 in these areas, or just don't bother upgrading -- one or the other. ================================ 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:
>OK ignoring obvious errors in code like ending brackets etc which may >have worked with 3 but would now crash with 4 are there _any_ >'tags/contexts/coding techniques' that do not work the same as 3 - >even if they don't actually crash 4? Yes of course! In fact, there are at least two MAJOR issues:1- If your coding techniques have used form variables to override text variables, your old code will break. This coding technique was always the default before, but beginning with version 4 this has changed ...2- If your coding techniques have used a space character in field or variable names, your old code will break. The only solution is to recode your old sites to get rid of the spaces if you want them to work with version 4. By the way, before John Peacock jumps in here (again) and tries to make an issue out of the fact that it is stupid to use spaces in field and variable names, just let me say this once again, so everyone knows the TRUTH and the FACTS regarding the use of spaces in the webdna language:1- Spaces have *always* been acceptable field and variable name characters -- until version 4. This is a fact.2- Grant Hulbert, the webcatalog software engineer, specifically told me (years ago) that we *can* use space characters in field and variable names. He said he coded webcatalog *specifically* to deal with space characters in field and variable names exactly the same as any alphanumeric character would be dealt with in the same place.And he was right -- until version 4, that it.3- In other words, it has never been 'wrong', nor has it ever been 'stupid', to use spaces in field and variable names. After all, the webdna language was coded specifically to ALLOW us to use spaces in these places with no problem -- until version 4.4- It is only now, with the release of version 4, that SM has decided to eliminate space characters as acceptable field and variable name characters in webcatalog. This means if you have ever used spaces in these places previously, your old sites will fail unless you upgrade them to match the more limited capabilities of version 4 in these areas, or just don't bother upgrading -- one or the other. ================================ 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:
PIXO support (1997)
Search on Dates (2000)
Generating Options for a Form. (1997)
Emailer (1997)
ShowNext (1997)
[OT] search engine Q (2001)
[append] vs. [appendfile] delta + question? (1997)
[showif] Saturday won't work (2007)
profiles (1999)
Getting Emailer to send mail (1997)
Trouble with formula.db (1997)
value in forms (2000)
ListVariables Problem (2003)
stumped on simple sort (1999)
WebCat Refrence problem (2000)
Secure server question (1997)
Authenticating via SQL server (2005)
Friendly , quick 'security' check, please (2003)
Requiring that certain fields be completed (1997)
Passing WebCat Vars with Javascript (2000)