Error Lob.db records error message not name

This WebDNA talk-list message is from

1997

It keeps the original formatting. numero = 10887
interpreted = N
texte = Grant,I think it would be a lot better if the ErrorLog database recorded the'Name' of the error message and not the 'Message' itself. Here's why ...I've been using the admin interface today and I see that when I click the'Show Error Log' link, it opens the ErrorLog.db and feeds every record ontomy screen ... or at least it tries to.The problem is that WebCat2 doesn't simply display the 'name' of the error,it displays the 'message' for each error, several of which I havecustomized to include full HTML text. When I click the 'Show Error Log'link, it tried to display all this HTML text inside the [founditems] loop,and if too many HTML error messages are 'found', my browser crashes.We don't really need to see the text of the error messages anyways, what wereally need is the 'name' of the error - I think that would be enough forus to track down problems. And it would prevent the ErrorLog.db fromgetting so huge, too.Do you or anyone else on the list think this is a reasonable request for achange in the next beta?Sincerely, Ken Grome .......... ken@iav.com .......... :) Associated Messages, from the most recent to the oldest:

Re: Error Lob.db records error message not name (Kenneth Grome 1997) Re: Error Lob.db records error message not name (grichter@panavise.com (Gary Richter) 1997) Re: Error Lob.db records error message not name (Grant Hulbert 1997) Re: Error Lob.db records error message not name (grichter@panavise.com (Gary Richter) 1997) Re: Error Lob.db records error message not name (Grant Hulbert 1997) Error Lob.db records error message not name (Kenneth Grome 1997)

Grant,I think it would be a lot better if the ErrorLog database recorded the'Name' of the error message and not the 'Message' itself. Here's why ...I've been using the admin interface today and I see that when I click the'Show Error Log' link, it opens the ErrorLog.db and feeds every record ontomy screen ... or at least it tries to.The problem is that WebCat2 doesn't simply display the 'name' of the error,it displays the 'message' for each error, several of which I havecustomized to include full HTML text. When I click the 'Show Error Log'link, it tried to display all this HTML text inside the [founditems] loop,and if too many HTML error messages are 'found', my browser crashes.We don't really need to see the text of the error messages anyways, what wereally need is the 'name' of the error - I think that would be enough forus to track down problems. And it would prevent the ErrorLog.db fromgetting so huge, too.Do you or anyone else on the list think this is a reasonable request for achange in the next beta?Sincerely, Ken Grome .......... ken@iav.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:

WC2b15 - [HTMLx]...[/HTMLx] problems (1997) international time (1997) [off] Promotions Co? (1997) [BoldWords] WebCat.acgib15Mac (1997) webcat feature request (1997) WebCat2b13MacPlugIn - More limits on [include] (1997) WebCat2: Items xx to xx shown, etc. (1997) international time (1997) Re[2]: 2nd WebCatalog2 Feature Request (1996) Problems setting MIME Headers (1998) Grepping spaces (2004) PCS Frames (1997) WebCat & WebTen (1997) Re:trouble (1997) Problems getting parameters passed into email. (1997) Not really WebCat (1997) Banner Ads (2000) empty order (2004) using showpage and showcart commands (1996) Multiple Ad databases? (1997)