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 onto my 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 have customized 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 we really need is the 'name' of the error - I think that would be enough for us to track down problems. And it would prevent the ErrorLog.db from getting so huge, too.Do you or anyone else on the list think this is a reasonable request for a change in the next beta?Sincerely, Ken Grome .......... ken@iav.com .......... :)
Associated Messages, from the most recent to the oldest:
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 onto my 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 have customized 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 we really need is the 'name' of the error - I think that would be enough for us to track down problems. And it would prevent the ErrorLog.db from getting so huge, too.Do you or anyone else on the list think this is a reasonable request for a change 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:
WebCat2 beta FTP site (1997)
Server capacity (2003)
Make sure I understand this??? (1997)
same products but different (1998)
date format (another question) (2000)
restart needed???? (1997)
alternatives for WebDNA (2004)
Cookie Newbie (2002)
[WebDNA] .html extension (2012)
Sendmail truncation in Eudora Clients (1998)
Feature Request : Separate [search] and [founditems] (2002)
[WebDNA] Cacheing include files (2015)
PR: WebCatalog Affiliates Program Announced -- Share the revenue for promoting WebCatalog (2000)
required fields (1999)
F3 crashing server (1997)
Re[3]: Charting records by state (2000)
Change 2.0 to 2.1: Carts files not written to disk automatically (1998)
Applying discounts as more items are added... (1997)
RE: type 2 errors with ssl server (1997)
WebCat2b12 CGI Mac - [shownext] problem (1997)