Thanks for this plugin, its made debugging less of a pain.
I know as a feature it takes the log file and reverses the order so you can see the last item first. However, if the log entry is more than one line long, it gets reversed too.

So I log arrays (via print_r) sometimes and it ends up looking like this:

)
[updated_at] => 2012-11-20 05:19:28
[created_at] => 2012-11-20 05:19:28
[spot] => 4
[id] => 2
(
2012-11-20 05:19:28 SAVESPOT - Array

instead of this:

2012-11-20 05:19:28 SAVESHOOTER - Array
(
[id] => 2
[spot] => 4
[created_at] => 2012-11-20 05:19:28
[updated_at] => 2012-11-20 05:19:28 
)

Maybe instead of exploding on every new line, regex for a date or something.

My app is not in the root off the website.
and the style.css is not loading since the path to it is not correct...
Therefore I replaced in your view file ' viewer.php'

    <link href="<?php echo Bundle::assets('logviewer'); ?>style.css?1" rel="stylesheet" type="text/css">

into

    <?php 
    $assets = Asset::container('container')->bundle('logviewer');
    $assets->add('style','style.css');
    echo $assets->styles();
    ?>

Could you apply such change?

Thanks for the bundle.
Bye,
Karel.

Hi,

I just started using Laravel yesterday, and yours is the first bundle I tried. How cool is that?

A thought for dummies like me who arrived at the framework a day ago, you might add something like the following to the documentation.

"To enable and use logging, see the instructions at http://laravel.com/docs/logging. To view the log files, navigate to /logviewer".

It wasn't too hard to dig that information up, but being obvious is good. :)

Thanks again for the bundle.

John

What would be the best way to implement a security layer over the logviewer, besides a complicated URI?