This allows if in the feature we want to create a new featured that include patterns we cant add this for the best readability (some patterns get really complicated)

Got this error after following the installation instruction for Lumen: Class App\Http\Controllers\Rap2hpoutre\LaravelLogViewer\LogViewerController does not exist

FYI, the route's settings file in Lumen 5.3 is on: routes/web.php

Im a newbie with laravel, but did all as in the README of this package and when I go to http://myapp/logs I get this error:

InvalidArgumentException in compiled.php line 12896: No hint path defined for [laravel-log-viewer]

Any ideas on why this happens?

Thanks.

Just did a composer update on a Laravel project and now it's showing.

Class Rap2hpoutre\LaravelLogViewer\LogViewerController does not exist

This was working fine before the composer update

Thank you.

In response to issue #202 where the package doesn't detect other log files deep in the year and month folders. I modified the package to generate an array of the directory structure with the files therein so user can click on any file to view logs.

Instead of loading an entire logfile in one go, can we use AJAX to fetch just the rows that are needed? Datatable is really good at this, and it is surprisingly easy to do with a package to handle the server side, such as https://github.com/yajra/laravel-datatables

It would be awesome if the page would automatically update when there are new items to show.

Ideally, this would be done with sockets. I don't have a lot of experience with sockets in PHP, but I've found it's not nearly as easy as say, Node and socket.io.

I'm really not sure how viable this is in pure PHP (i.e. I don't know that you can really watch for file changes in realtime with PHP), but it would be a super useful feature! Definitely possible and not terrible difficult with Node, but that'd require another dependency.

Just wanted to throw this out there and see if anyone else had any ideas.

Encrypter.php -> getJsonPayload waits payload to be json_decodeable bash64 encrypted data. But the payload comes as base64 encoded string of log file name (lumen-2018-04-19.log). So selecting log file throws an invalid payload exception.

Updated to latest 0.13, and using Lumen 5.6 latest. (Lumen - not Laravel.)

Setup has always worked. Now whenever we hit our /logs endpoint, we get the following:

Class 'Crypt' not found (View: \/var\/www\/server\/vendor\/rap2hpoutre\/laravel-log-viewer\/src\/views\/log.blade.php

Our web.php is as required:

$router->group(['namespace' => '\Rap2hpoutre\LaravelLogViewer'], function () use ($router) {
    $router->get('logs', 'LogViewerController@index');
});

And yes we have the appropriate line in app.php:

// Lumen.log viewer.
$app->register(\Rap2hpoutre\LaravelLogViewer\LaravelLogViewerServiceProvider::class);

Simply cannot get past this error. I don't know if it's related to the Lumen upgrade to 5.6, the upgrade to 0.13 for the log viewer itself, or a combination of the two.

Please help. Thanks.

Hi all,

I hope you are doing fine. Do we have any option to define multiple locations e.g. via config setting storage_path to array = ['/location1', '/other/location2']?

Thank you.

Hey, as the title suggests, vendor:publish doesn't publish a thing. It doesn't give me an error, just tells me that publishing is complete though. If I manually copy the log.blade.php into views/vendor/laravel-log-viewer and edit that file, then I can see my changes.

this package is work fine in local but when I move to the host I get this error

This page isn’t working xxxxx.com is currently unable to handle this request. HTTP ERROR 500

can anyone help me pls ?

When a log entry contains a level keyword like "failed" and a colon afterwards, an additional log entry with everything after the keyword + colon gets shown in the log viewer.

Example: [2022-11-13 13:13:33] local.WARNING: Request failed: reason test

Reproducable with: Log::warning("Request failed: reason test");

Gets shown as:

Initially I encountered an issue where logging throw new \Exception('failed: test'); would result in the code recognizing 2 log inputs (because of the "failed" word). After trying to debug the issue I found that the whole pattern matching was written very inefficiently so I cleaned up that code and improved the algorithm to a more stable solution, which matches using a much more straightforward technique:

• All log entries start with a date part (e.g. [2022-09-16 13:19:40]) up until the next occurrence of any such date string, indicating a new log entry has been encountered
• This log entry is then divided into a heading and a stacktrace, simply using a separation on the first linebreak \n (which seems to be the default for all monolog entries)

All code should still work for PHP 5.4 (although I havent tested that outdated dependency)

Laravel: 9.27.0 laravel-log-viewer: 2.2.0 PHP 8.1.7

basename(): Passing null to parameter #1 ($path) of type string is deprecated in /Users/rajjanorkar/Projects/myproject/vendor/rap2hpoutre/laravel-log-viewer/src/Rap2hpoutre/LaravelLogViewer/LaravelLogViewer.php on line 141

I believe this only happens when i delete all log files.

When I exported log.blade.php to views. After that, I ran artisan optimize:clear and errors.

Illuminate\\Contracts\\Container\\BindingResolutionException: Target class [view] does not exist. in /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php:877

Please help me. Thank you so much!