Open malle-pietje opened 1 year ago
Hello there! Thanks for opening your first issue on this repo!
Just a heads-up: Here at Backpack we use Github Issues only for tracking bugs. Talk about new features is also acceptable. This helps a lot in keeping our focus on improving Backpack. If you issue is not a bug/feature, please help us out by closing the issue yourself and posting in the appropriate medium (see below). If you're not sure where it fits, it's ok, a community member will probably reply to help you with that.
Backpack communication mediums:
backpack-for-laravel
tag;Please keep in mind Backpack offers no official / paid support. Whatever help you receive here, on Gitter, Slack or Stackoverflow is thanks to our awesome awesome community members, who give up some of their time to help their peers. If you want to join our community, just start pitching in. We take pride in being a welcoming bunch.
Thank you!
-- Justin Case The Backpack Robot
Hey @malle-pietje sorry it took so much time to get into this.
We indeed need a better log viewer, unfortunately this had not been a priority and I am afraid it will continue like that at least until we launch v6 (due next months).
Sorry I have nothing new to add here, just to let you know isn't forgotten 👍
Cheers
Bug report
What I did:
Use LogManager to view all log files in the
storage/logs
directory.What I expected to happen:
Either be able to preview non-Laravel log files with less functionality or get an appropriate error message informing the user that the log file isn't parsable.
What happened:
The error shown when trying to preview a Laravel schedule log file says "The log file doesn't exist":
But the log file does exist, even though it isn't a regular Laravel log file.
This is an example of such a schedule log file populated by a "chatty" class that fetches data from an external API containing test data:
What I've already tried to fix it:
Nothing yet.
Backpack, Laravel, PHP, DB version:
Backpack CRUD: 5.4.10 Backpack LogManager: 4.0.8 PHP: 8.1.2