Re: Signal Raised Error (Part II)

This WebDNA talk-list message is from

1997

It keeps the original formatting. numero = 12589
interpreted = N
texte = >I'm finding that I have to clean out the error log every couple of days.There are a couple of things you can do. The file called ErrorTemplate.tmpl controls what goes into the error log, so you can change that in a few ways:1) take all the text out of ErrorTemplate.tmpl, so it does no logging whatsoever2) change it to[appendfile file=/WebCatalog/ErrorLog.txt&secure=F][date] [time] [command] [ipaddress] [errormessage][/appendfile]so it doesn't treat the error log like a database (and therefore won't get sucked into RAM)3) wrap some WebDNA around the existing logging code so it ignores authorization failures that are caused by empty username/passwords (the most common cause)Maybe something like:[showif [errormessage]^Not Authorized][hideif [username]=]...previous contents of ErrorTemplate.tmpl...[/hideif][/showif]which I'm sure is not exactly right, but it illustrates the idea of hiding the error log if the username is blank and the error was an authorization error.>Maybe I'm using the [protect] tag incorrectly. Here is the code I have on all of my protected pages. Protected meaning subscriber only access areas.You're using it just fine. [Protect] actually makes use of the [Authenticate] tag as one of its tools, and in fact [Protect groupname] is just shorthand for [Include file=/MultiGroupChecker&groups=groupname]If you look at MultiGroupChecker, you'll see exactly the source WebDNA for the [protect] tag, so you can write your own that mimics it (perhaps using your own users.db database).Grant Hulbert, V.P. Engineering | ===== Tools for WebWarriors =====Pacific Coast Software | WebCatalog Pro, WebCommerce Solution11770 Bernardo Plaza Court | SiteEdit Pro, SiteCheck, PhotoMasterSan Diego, CA 92128 | SiteGuard619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com Associated Messages, from the most recent to the oldest:

Re: Signal Raised Error (Part II) (Grant Hulbert 1997)
Re: Signal Raised Error (Part II) (Mark Anderson 1997)

>I'm finding that I have to clean out the error log every couple of days.There are a couple of things you can do. The file called ErrorTemplate.tmpl controls what goes into the error log, so you can change that in a few ways:1) take all the text out of ErrorTemplate.tmpl, so it does no logging whatsoever2) change it to[appendfile file=/WebCatalog/ErrorLog.txt&secure=F][date] [time] [command] [ipaddress] [errormessage][/appendfile]so it doesn't treat the error log like a database (and therefore won't get sucked into RAM)3) wrap some WebDNA around the existing logging code so it ignores authorization failures that are caused by empty username/passwords (the most common cause)Maybe something like:[showif [errormessage]^Not Authorized][hideif [username]=]...previous contents of ErrorTemplate.tmpl...[/hideif][/showif]which I'm sure is not exactly right, but it illustrates the idea of hiding the error log if the username is blank and the error was an authorization error.>Maybe I'm using the [protect] tag incorrectly. Here is the code I have on all of my protected pages. Protected meaning subscriber only access areas.You're using it just fine. [protect] actually makes use of the [authenticate] tag as one of its tools, and in fact [Protect groupname] is just shorthand for [Include file=/MultiGroupChecker&groups=groupname]If you look at MultiGroupChecker, you'll see exactly the source WebDNA for the [protect] tag, so you can write your own that mimics it (perhaps using your own users.db database).Grant Hulbert, V.P. Engineering | ===== Tools for WebWarriors =====Pacific Coast Software | WebCatalog Pro, WebCommerce Solution11770 Bernardo Plaza Court | SiteEdit Pro, SiteCheck, PhotoMasterSan Diego, CA 92128 | SiteGuard619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com Grant Hulbert

DOWNLOAD WEBDNA NOW!

Re: Signal Raised Error (Part II)

1997

Top Articles:

Related Readings: