On Tue, September 9, 2014 13:22, Paul Lesniewski wrote:
>
> Things don't go blank without an error somewhere. Increase your
> logging verbosity? Go back to default configuration file for the
> plugin? Keep digging.
>
The problem was, as you suggested, with the config.php file. The statement
$
Paul, I'll send you the message direct rather than to the list
View headers reports:
Return-Path:
Received: from mail.amagic.in.ua (91.217.254.212.hostpark.com.ua
[91.217.254.212] (may be forged))
by cyber7.csz.com (8.14.4/8.14.4/Debian-4) with ESMTP id s890eTCX018260
for ; Mon, 8 Sep 2
On 9/9/14, James B. Byrne wrote:
>
> On Tue, September 9, 2014 03:08, Paul Lesniewski wrote:
>> On 9/8/14, James B. Byrne wrote:
>>> The problem I am experiencing is that whenever I enable the
>>> squirrel_logger
>>> Logging plugin then the SM web app blanks the web page and becomes
>>> non-respo
On Tue, September 9, 2014 03:08, Paul Lesniewski wrote:
> On 9/8/14, James B. Byrne wrote:
>> The problem I am experiencing is that whenever I enable the squirrel_logger
>> Logging plugin then the SM web app blanks the web page and becomes
>> non-responsive when a user opens a new or logs out of
On 9/8/14, James B. Byrne wrote:
> The problem I am experiencing is that whenever I enable the squirrel_logger
> Logging plugin then the SM web app blanks the web page and becomes
> non-responsive when a user opens a new or logs out of an existing SM
> session.
This is a FAQ in the list archives.
