Enhancement request: error ticket and explanation on same page

[weheh]

I wonder why error tickets are implemented in such a way that the
ticket shows up as a single hypertexted line on a page, which you have
to click to see the actual error message? Why not have the error
message details listed immediately after the ticket number? I'm pretty
sure that would save me hundreds of clicks a day. Is it possible that
all the rest of you out there only see a couple/few error messages a
day? ;^)

[Álvaro Justen [Turicas]]

User of your site will see ticket but only the administrator/developer
(you) will have access to admin to view the ticket, TraceBack etc.
Information of errors must be hide to users for security reasons.

--
Álvaro Justen
Peta5 - Telecomunicações e Software Livre
21 3021-6001 / 9898-0141
http://www.peta5.com.br/

[Yarko Tymciurak]

On Mon, May 4, 2009 at 1:38 AM, Álvaro Justen [Turicas] <alvaro...@gmail.com> wrote:

On Mon, May 4, 2009 at 3:32 AM, weheh <richard...@verizon.net> wrote:
> I wonder why error tickets are implemented in such a way that the
> ticket shows up as a single hypertexted line on a page, which you have
> to click to see the actual error message?

..... 

User of your site will see ticket but only the administrator/developer
(you) will have access to admin to view the ticket, TraceBack etc.
Information of errors must be hide to users for security reasons.

Also, it's handy to have ticket open in another tab / window - work on error, and reload the original (see if it works the second time, if that's appropriate), or back...  you get the idea...

Anyway, with something like WingIDE, you catch the error before the ticket number & ticket code ensues, so you have a chance to review, change immediately..... _that's_ really nice for the repetative cycles you're talking about.

Lacking that, you can reduce some steps by running 2 things in parallel - your web2py instance in browser, and a second web2py shell, where you can try commands individually to check output before you put them all together and test in the browser instance.  (the WingIDE method sort of lets you unify all this).