Couldn't an easy command like "php -l config.php" be added to the configtest? I
have just tested it for a trailing colon like it happened and it will complain.
Should someone add a bug or request or patch for this?
Further, it will complain about many other simple mistakes we could probably
mis
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
$
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.
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.
Setup.
CentOS-6.5 x86_64
Server version: Apache/2.2.15 (Unix) Server built:
