How to eliminate the traceback in the error message screen?
When i key in the duplicate record ZOPE will prompt out the duplicate error message, actually i can just modified the top part of this error message screen but i want to eliminate the traceback show on the bottom of the page but i dont know where to modify it. Please let me know as soon as possible. Thank You very much!!!! _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Hi angie, we all are in a quench when error happens. So we all need answers ASAP. And there is no user group like Zope's in this request. The traceback only shows up when Zope is started in debug mode. Which is done by using the -D flag on the command line. No -D no traceback (at least I believe so) Robert ----- Original Message ----- From: "angie tel" <angietel@hotmail.com> To: <zope@zope.org> Sent: Saturday, June 30, 2001 6:11 AM Subject: [Zope] How to eliminate the traceback in the error message screen?
When i key in the duplicate record ZOPE will prompt out the duplicate error message, actually i can just modified the top part of this error message screen but i want to eliminate the traceback show on the bottom of the page but i dont know where to modify it. Please let me know as soon as possible. Thank You very much!!!!
_________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Robert Rottermann wrote:
The traceback only shows up when Zope is started in debug mode. Which is done by using the -D flag on the command line.
Half true, it puts it in an HTML comment in production mode. What I don't understand is why it needs to do this. Why not just put the traceback code in standard_error_message and then the user can decide whether or not they want it to be displayed. For example, I'd only like people with the Manager role to see this stuff. cheers, Chris
Hi Chris, I think this problem is since the early stages in the collector :-) Even worser, this appended comment breaks all HTML (and WML or whatever). There was a patch on the mailinglist long long time ago. Unfortunately I was to lazy to catch it. So if someone manages to find it again or find the piece of code where it has to be applied... we should really fix this now :-) Regards Tino --On Sonntag, 1. Juli 2001 14:46 +0100 Chris Withers <chrisw@nipltd.com> wrote:
Robert Rottermann wrote:
The traceback only shows up when Zope is started in debug mode. Which is done by using the -D flag on the command line.
Half true, it puts it in an HTML comment in production mode.
What I don't understand is why it needs to do this. Why not just put the traceback code in standard_error_message and then the user can decide whether or not they want it to be displayed.
For example, I'd only like people with the Manager role to see this stuff.
cheers,
Chris
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Tino Wildenhain wrote:
There was a patch on the mailinglist long long time ago. Unfortunately I was to lazy to catch it. So if someone manages to find it again or find the piece of code where it has to be applied... we should really fix this now :-)
Yes, and in the Zope core too :-) That said, for it to be broken for this long means there must be godo reasons why it hasn't been fixed. Can anyone from DC shed some light? cheers, Chris
Is it a programmer error or a user error? A programmer error that says "something is wrong" with no advice about how to find it could get really frustrating. (sorry, I'm not from DC, just opionionated :-) At 13:38 03/07/01 +0100, Chris Withers wrote: <snip>
That said, for it to be broken for this long means there must be godo reasons why it hasn't been fixed. Can anyone from DC shed some light?
cheers,
Chris
participants (5)
-
angie tel -
Chris Withers -
J. Cone -
Robert Rottermann -
Tino Wildenhain