On Mon, May 4, 2009 at 1:38 AM, Álvaro Justen [Turicas] < [email protected]> wrote:
> > On Mon, May 4, 2009 at 3:32 AM, weheh <[email protected]> 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). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
