Skip Menu |

This queue is for tickets about the Plack-Middleware-Debug-Log4perl CPAN distribution.

Report information
The Basics
Id: 106653
Status: new
Priority: 0/
Queue: Plack-Middleware-Debug-Log4perl
People
Owner: Nobody in particular
Requestors: kes-kes [...] yandex.ru
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Tue Aug 25 09:31:16 2015 kes-kes [...] yandex.ru - Ticket created
Subject: Ambigiour info in doc
Log4perl appender using TestBuffer, named 'log4perl_debug_panel'. But later in config example you use different name for it: log4perl.appender.DebugPanel.name = psgi_debug_panel What is right name? a) psgi_debug_panel b) log4perl_debug_panel
  Tue Aug 25 20:30:31 2015 ether [...] cpan.org - Subject changed from 'Ambigiour info in doc' to 'Ambiguous info in doc'
  Thu Aug 27 07:48:45 2015 kes-kes [...] yandex.ru - Correspondence added
From: kes-kes [...] yandex.ru
@@ -132,7 +129,7 @@ Ideally configure Log4perl using Plack::Midleware::Log4perl, or directly in your .psgi file. This way we can hook into the root logger at run time and create the required stealth logger automatically. If you're able to do this, you can skip the next bit. -For applications that configure / init their own logger, you must create a Log4perl appender using TestBuffer, named 'log4perl_debug_panel'. +For applications that configure / init their own logger, you must create a Log4perl appender using TestBuffer, named 'psgi_debug_panel'. In your Log4perl.conf:
  Thu Aug 27 07:50:31 2015 kes-kes [...] yandex.ru - Correspondence added
From: kes-kes [...] yandex.ru
This is not required at all: --- Log4perl.pm.orig 2015-08-26 05:18:58.000000000 +0000 +++ Log4perl.pm 2015-08-27 11:49:44.017904216 +0000 @@ -118,7 +115,6 @@ =head1 SYNOPSIS use Plack::Builder; - use Plack::Middleware::Debug::Log4perl; builder { enable 'Debug', panels => [qw/Memory Timer Log4perl/];