= Description =

Feature request: add the ability for a Wiki to disable the verbose debugging output (which shows installation paths, versions, hostnames, etc).  (This is also CVE-2007-0902)

== Steps to reproduce ==
## Describe the steps needed to reproduce the bug. If we can't reproduce it, we  probably can't fix it.
 1. Hit an exception in MoinMoin: [[http://moinmoin.wikiwikiweb.de/?action=info&general=exception]]
 2. Observe too many details: {{{Platform: Linux web.thinkmo.de 2.6.17-thinkmo-1 #1 SMP Sat Jul 29 17:36:42 CEST 2006 x86_64}}}

== Example ==
##Add URL that show the bug, screenshot or test wiki markup that fail...

##URL: 

##attachment:screenshot.png

##{{{
##Example wiki markup that fail
##}}}

Add "show_traceback" option to configuration.  Retain current behavior by defaulting to "1".

== Component selection ==

## Where you think is this bug happening ? (general, plugin [plugin name], theme [theme name], ...

 * failure.py

== Details ==

## If you got a traceback, please save the traceback page as html and attach here:
## attachment:traceback.html

## if the bug is in this wiki, just kill the table and write: This Wiki.

## If a traceback is not available, please fill in the details here:
See attached patch for a possible solution: [[attachment:add-show_traceback.diff]]

== Workaround ==
## How to deal with the bug until it is fixed
None.

= Discussion =

The suggested solution assume that the wiki configuration is accessible, which is not true if your configuration is broken. This is the reason we chose to use a combination of environment variable (set in you main script) and a request parameter, which can be added in the url.

The change should be this:

 1. The default should be to save tracebacks to a safe log file on the server. If a log was saved, the error can display the name of the saved traceback.
 2. Environment variable or request parameter can be used to enable tracebacks

Extensions:

 1. If a request parameter was given but request parameters are not accessible (e.g request code is broken), a traceback will be saved to disk.

----
I think there should be a better solution. Just dumping the traceback to some file on the server makes debugging harder, as it involves more people and more effort to get a traceback to moin development. Maybe some email-based solution, sending the traceback to some configured email address? -- ThomasWaldmann <<DateTime(2007-03-17T13:22:56Z)>>

= Plan =
## This part is for Moin``Moin developers:

 * Priority: 
 * Assigned to: ThomasWaldmann
 * Status: feature added to 1.5 branch (together with a notice about that we will reject bug reports when not enough information is given)

----
## If you are a moin core developer, replace the category to Category* in these cases:
## Category MoinMoinNoBug - if this is not a bug.
## Category MoinMoinBugConfirmed - if you can confirm the bug on current code.
## Category MoinMoinBugFixed - after the bug is fixed in current code.
CategoryMoinMoinBugFixed