- What is graham-campbell/cms-logviewer used for?
- It is a CMS Core plugin that adds a LogViewer admin module to Graham Campbell's CMS, letting administrators browse, search, and inspect application log files directly from the dashboard. It removes the need for direct server access when debugging a Laravel application. It is a lightweight admin add-on rather than a standalone log management platform.
- Which Laravel versions does cms-logviewer support?
- The package explicitly supports only Laravel 4.1, according to its own constraint. Laravel 4.1 reached end of life in 2014 and does not run on PHP 7 or later, so the package fits only the corresponding PHP 5.4 to 5.6 era runtime. There is no support for Laravel 5+, Lumen, or any modern Laravel release.
- How do I install graham-campbell/cms-logviewer?
- Install it with Composer from inside a Laravel 4.1 application running a compatible PHP version. Because the latest release is v0.2.0-alpha with no documented backwards compatibility guarantees, pin the exact alpha tag instead of using a floating constraint. Then register and enable the plugin through Graham Campbell's CMS admin module configuration.
- Does cms-logviewer work with Laravel 8, 9, 10, or 11?
- No. The package's service provider, facades, and Eloquent model assumptions are tied to Laravel 4.1 APIs, so it will not install or run on modern Laravel versions without a fork. Teams on a current stack should treat it as reference material or a fork candidate rather than a dependency.
- Will the PSR-4 migration in v0.2.0-alpha break existing integrations?
- Yes, it can. Any consumer relying on the previous class locations, classmap autoloading, or non-namespaced references will break now that the package uses PSR-4 autoloading and PSR naming conventions. Diff the public API surface against the prior tag and verify class resolution before upgrading. The release also mentions model refactoring that is not itemized, so review public method signatures as well.
- Is cms-logviewer safe to use in production?
- Use caution: the only current release is an alpha, and it targets a Laravel version that no longer receives security patches. The release notes mention authentication and event improvements plus removed broken tests, which makes verified behavior harder to trust. If you must run it, freeze on a known tag, review the public API diff, and exercise the auth and event flows in staging first.
- Can administrators search and browse log files with cms-logviewer?
- Yes, the module lets administrators browse, search, and inspect application log files from the CMS dashboard. That covers routine debugging without SSH or server filesystem access. The exact filtering and display options are not documented in detail, so confirm them against your own log formats in a staging environment.
- Are there alternatives to cms-logviewer for viewing Laravel logs?
- Yes. Modern Laravel applications have actively maintained options such as Rap2hpoutre/laravel-log-viewer and opcodesio/log-viewer, both of which support current Laravel versions and PHP runtimes. For Graham Campbell's CMS specifically, cms-logviewer remains the matching admin module. If you need dashboard-based log browsing today, one of those packages is the more practical choice.
- Is cms-logviewer still maintained?
- The repository now lives under the GrahamDeprecated organization, which signals the line is legacy or archived rather than actively developed. The most recent release is an alpha and its supported framework is long past end of life. Treat release cadence and maintainer commitment as unverified, and plan for a fork if you need fixes.
- How do I migrate cms-logviewer to a modern Laravel version?
- Fork or vendor the package, then replace the Laravel 4.1 service provider and facade wiring with current equivalents. Re-target the refactored Eloquent models to modern Eloquent and rebuild the test suite, since the removed tests leave coverage uncertain; the PSR-4 autoloading and PSR naming already in place reduce some of that work. Expect a small to medium effort depending on how much of the authentication and events logic is reusable.