[Zope-dev] standard_error_message manipulation

2001-04-09 Thread Dyon Balding

Hi,

As part of a large python product I wanted to modify the normal
"Zope Error" standard_error_message page.

Most exceptions will be caught in the code, and therefore those
that do get through and cause an error message to be displayed
to the user probably indicate a bug in our code.  I would like
to give the user the ability to submit the details of the exception
along with their own information as a bug report.

I created my own standard_error_message, and wanted it to contain
a form with the values of error_value and error_tb among
others.  It however appears that the values of these variables get
rendered into HTML much earlier than desired and therefore aren't
very readable in a bug report.

Is there a better approach to this problem? or a work around?

thanks
-d

-- 
Dyon Balding [EMAIL PROTECTED]

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] standard_error_message manipulation

2001-04-09 Thread Andy McKay

I run error_value through a simple python script to get the original message
back again :)

Cheers.
--
  Andy McKay.


- Original Message -
From: "Dyon Balding" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, April 09, 2001 9:44 PM
Subject: [Zope-dev] standard_error_message manipulation


 Hi,

 As part of a large python product I wanted to modify the normal
 "Zope Error" standard_error_message page.

 Most exceptions will be caught in the code, and therefore those
 that do get through and cause an error message to be displayed
 to the user probably indicate a bug in our code.  I would like
 to give the user the ability to submit the details of the exception
 along with their own information as a bug report.

 I created my own standard_error_message, and wanted it to contain
 a form with the values of error_value and error_tb among
 others.  It however appears that the values of these variables get
 rendered into HTML much earlier than desired and therefore aren't
 very readable in a bug report.

 Is there a better approach to this problem? or a work around?

 thanks
 -d

 --
 Dyon Balding [EMAIL PROTECTED]

 ___
 Zope-Dev maillist  -  [EMAIL PROTECTED]
 http://lists.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists -
  http://lists.zope.org/mailman/listinfo/zope-announce
  http://lists.zope.org/mailman/listinfo/zope )



___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] standard_error_message manipulation

2001-04-09 Thread Dyon Balding

argh! that wasn't the answer i was looking for :)

-d

On Mon, Apr 09, 2001 at 09:57:36PM -0700, Andy McKay wrote:
 I run error_value through a simple python script to get the original message
 back again :)
 
 Cheers.
 --
   Andy McKay.
 
 
 - Original Message -
 From: "Dyon Balding" [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Monday, April 09, 2001 9:44 PM
 Subject: [Zope-dev] standard_error_message manipulation
 
 
  Hi,
 
  As part of a large python product I wanted to modify the normal
  "Zope Error" standard_error_message page.
 
  Most exceptions will be caught in the code, and therefore those
  that do get through and cause an error message to be displayed
  to the user probably indicate a bug in our code.  I would like
  to give the user the ability to submit the details of the exception
  along with their own information as a bug report.
 
  I created my own standard_error_message, and wanted it to contain
  a form with the values of error_value and error_tb among
  others.  It however appears that the values of these variables get
  rendered into HTML much earlier than desired and therefore aren't
  very readable in a bug report.
 
  Is there a better approach to this problem? or a work around?
 
  thanks
  -d
 
  --
  Dyon Balding [EMAIL PROTECTED]
 
  ___
  Zope-Dev maillist  -  [EMAIL PROTECTED]
  http://lists.zope.org/mailman/listinfo/zope-dev
  **  No cross posts or HTML encoding!  **
  (Related lists -
   http://lists.zope.org/mailman/listinfo/zope-announce
   http://lists.zope.org/mailman/listinfo/zope )
 

-- 
Dyon Balding [EMAIL PROTECTED]

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] standard_error_message manipulation

2001-04-09 Thread Andy McKay

Sorry what answer would you like? :)

Cheers.
--
  Andy McKay.


- Original Message -
From: "Dyon Balding" [EMAIL PROTECTED]
To: "Andy McKay" [EMAIL PROTECTED]
Cc: "Dyon Balding" [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Monday, April 09, 2001 9:57 PM
Subject: Re: [Zope-dev] standard_error_message manipulation


 argh! that wasn't the answer i was looking for :)

 -d

 On Mon, Apr 09, 2001 at 09:57:36PM -0700, Andy McKay wrote:
  I run error_value through a simple python script to get the original
message
  back again :)
 
  Cheers.
  --
Andy McKay.
 
 
  - Original Message -
  From: "Dyon Balding" [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Sent: Monday, April 09, 2001 9:44 PM
  Subject: [Zope-dev] standard_error_message manipulation
 
 
   Hi,
  
   As part of a large python product I wanted to modify the normal
   "Zope Error" standard_error_message page.
  
   Most exceptions will be caught in the code, and therefore those
   that do get through and cause an error message to be displayed
   to the user probably indicate a bug in our code.  I would like
   to give the user the ability to submit the details of the exception
   along with their own information as a bug report.
  
   I created my own standard_error_message, and wanted it to contain
   a form with the values of error_value and error_tb among
   others.  It however appears that the values of these variables get
   rendered into HTML much earlier than desired and therefore aren't
   very readable in a bug report.
  
   Is there a better approach to this problem? or a work around?
  
   thanks
   -d
  
   --
   Dyon Balding [EMAIL PROTECTED]
  
   ___
   Zope-Dev maillist  -  [EMAIL PROTECTED]
   http://lists.zope.org/mailman/listinfo/zope-dev
   **  No cross posts or HTML encoding!  **
   (Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )
  

 --
 Dyon Balding [EMAIL PROTECTED]



___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )