Re: New 4.5 installer
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 40949
interpreted = N
texte = >The installer only checks for: > WebCatalogEngine/WebCatalog Prefs > WebCatalogEngine/Users.db > WebCatalogEngine/Triggers.db > WebCatalogEngine/Globals/WebMerchant/Stores.db It should also leave the errormessages.db alone.Many of us have replaced the values in some errormessages.db records in order to make webcat produce the proper error messages for our needs. Some of us even put webdna tags into those records in order to do things like [redirect] -- because that's the best way for us to deal with certain error situations.Please consider having your future installers simply append any *new* error messages to this db that are not currently in it -- then we won't have to worry about your installers screwing up our properly configured errormessages.db and the proper functioning of our web sites.Or here's an even better and more elegant solution:Consider rewriting webcat's internal code so that it tries to retrieve all error messages from a new customErrors.db file first, before going to the errormessages.db to retrieve an error message. This would let us store our custom error messages in a place where your installers won't mess with them, and your installers can always overwrite the existing errormessages.db without creating problems for us.What do you think? Would this be an improvement? I cannot imagine any reason why this would not be better for everyone involved ...A properly-written webdna site seldom has any hits to the errormessages.db anyways, so for webcat to check the customErrors.db file first -- before going to the errormessages.db -- would not create any unreasonable demands for system resources. And it would definitely eliminate the problem of SMSI installers destroying our custom error messages.Wouldn't it? Sincerely, Kenneth Grome------------------------------------------------------------- Kenneth Grome & Associates US-Asian Business Specialists Philippine Business Office +63 (32) 255-6921 Primary Email Address owner@kengrome.com Alternate Email Address kengrome@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:
>The installer only checks for: > WebCatalogEngine/WebCatalog Prefs > WebCatalogEngine/Users.db > WebCatalogEngine/triggers.db > WebCatalogEngine/Globals/WebMerchant/Stores.db It should also leave the errormessages.db alone.Many of us have replaced the values in some errormessages.db records in order to make webcat produce the proper error messages for our needs. Some of us even put webdna tags into those records in order to do things like [redirect] -- because that's the best way for us to deal with certain error situations.Please consider having your future installers simply append any *new* error messages to this db that are not currently in it -- then we won't have to worry about your installers screwing up our properly configured errormessages.db and the proper functioning of our web sites.Or here's an even better and more elegant solution:Consider rewriting webcat's internal code so that it tries to retrieve all error messages from a new customErrors.db file first, before going to the errormessages.db to retrieve an error message. This would let us store our custom error messages in a place where your installers won't mess with them, and your installers can always overwrite the existing errormessages.db without creating problems for us.What do you think? Would this be an improvement? I cannot imagine any reason why this would not be better for everyone involved ...A properly-written webdna site seldom has any hits to the errormessages.db anyways, so for webcat to check the customErrors.db file first -- before going to the errormessages.db -- would not create any unreasonable demands for system resources. And it would definitely eliminate the problem of SMSI installers destroying our custom error messages.Wouldn't it? Sincerely, Kenneth Grome------------------------------------------------------------- Kenneth Grome & Associates US-Asian Business Specialists Philippine Business Office +63 (32) 255-6921 Primary Email Address owner@kengrome.com Alternate Email Address kengrome@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:
How To question on setting up downloads (1997)
Another reviewer 'forgets' NT WebCatalog (1998)
Fields/Forms Processing (1998)
completed orders database (1997)
[ShowNext] (1997)
Mondo amounts of Mail [long] (1999)
[OT] XML Primer (2004)
Populating a db from a form textarea (2005)
searchable list archive (1997)
Webcat causing crashes left and right! (1997)
Running _every_ page through WebCat ? (1997)
Hiding HTML and page breaks (1997)
[ipaddress] (2003)
Changing price for a SLU based on options (size, etc.) (1997)
[FileInfo] (1998)
Help formatting search results w/ table (1997)
[date format] w/in sendmail (1997)
Getting real time CC's out of Australia (1998)
Help! (1996)
how to get s repeatedly in and out of a form? (1999)