The original issue (in email below) is definitely fixed (I get a nice Log::Report error from it). 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. 2. Without Log::Report turned on: *Error 500 - Internal Server Error* *Runtime Error* Undefined subroutine &Dancer2::Plugin::Auth::Extensible::login called at /Library/Perl/5.18/Dancer2/Plugin/Auth/Extensible.pm line 282. /Library/Perl/5.18/Dancer2/Plugin/Auth/Extensible.pm around line 282 277 { 278 $app->request->parameters->set('password_code_valid' => 1), 279 } 280 281 no strict 'refs'; 282 return &{ $weak_plugin->login_page_handler }($weak_plugin); 283 }, 284 ); 285 286 $app->add_route( 287 method => 'get', Note that the log file does contain the full report (ie. this is a workable problem, in that I can just go to the log file for the full detail of the issue). cheers, Nathan On 10 February 2017 at 04:08, Andrew Beverley <andy@andybev.com> wrote:

On Tue, 7 Feb 2017 Andrew Beverley <andy@andybev.com> wrote:

...

On Thu, 5 Jan 2017 Nathan Bailey <web@polynate.net> wrote:

...

Hi all (especially Andy :-)

Sorry for the delay on this Nathan.

...

What are you supposed to put in your non-main route handlers? use Dancer2::Plugin::LogReport mode => 'DEBUG'; (like main route handler); OR use Log::Report; (like other modules)

I can now say that it /should/ be the same as any other route handlers. So wherever you have:

use Dancer2;

You should also have:

use Dancer2::Plugin::LogReport ...

Although if you're using the same appname (appname => ...) then you only need to use Log::Report.

The reason being that otherwise the required logging hook isn't inserted into that particular app.

However, there is a problem with the way the current version of the plugin works, which means that the correct DSL isn't always available to it. This will cause some unexpected behaviour. I'm working on a fix at the moment.

Fix included in aforementioned v1.19 Log::Report release. Let me know if you run into any other problems.

Regards,

Andy _______________________________________________ dancer-users mailing list dancer-users@dancer.pm http://lists.preshweb.co.uk/mailman/listinfo/dancer-users