[dancer-users] Less granularity from Log::Report than default logging (Was: RESOLUTION: Dancer2::Plugin::LogReport - basic setup)

Andrew Beverley andy at andybev.com
Mon Apr 3 08:39:29 BST 2017

On Mon, 3 Apr 2017 16:15:29 +1000 Nathan Bailey wrote:
> The original issue (in email below) is definitely fixed (I get a nice
> Log::Report error from it). 

Great, pleased to hear.

> In a similar vein, however, there is a difference in feedback to the
> browser with Dancer2::Plugin::Auth::Extensible (trying to get my
> customised login page working).
> 1. With Log::Report turned on:
> Internal Server Error
> Can't call method "uri" on an undefined value at
> /Library/Perl/5.18/Dancer2/Plugin/LogReport.pm line 228.

Sorry, that is actually a bug which I noticed before, but didn't get
round to fixing. I'll take a look today.

The idea is that the page *will* display minimal information, but it
should be useful minimal information, not the rather useless error that
you received.

If show_errors is true, then it will normally fallback to rendering the
page configured at forward_url (with the error in session.messages), or
if that can't be displayed then it will just bork as standard.

If show_errors is false, then session.messages will display a generic
"An unexpected error has occurred" (configurable) and the full stack
will be in whichever logging dispatcher is configured.


More information about the dancer-users mailing list