Weave Code
Laravel Admin Laravel Package
php-panel/laravel-admin
A Laravel admin panel package for quickly building back-office interfaces with CRUD screens, authentication, and customizable resources. It helps developers scaffold admin dashboards while keeping control over models, forms, and UI, making routine management tasks faster to implement and easier to m...
Build a full-featured administrative interface in ten minutes.
Frequently asked questions about Laravel Admin
- How do I install php-panel/laravel-admin?
- Install it with Composer using composer require php-panel/laravel-admin, then publish the package config and assets, run the admin migrations, wire the auth guard, and register the admin routes. For a new Laravel 13 app, use the 3.1.x line because v3.1.0 is the first release with a Laravel 13 compatibility target. Check the package composer.json for the exact framework and PHP constraints before installing.
- Does php-panel/laravel-admin support Laravel 13?
- Yes, v3.1.0 explicitly adds a Laravel 13 compatibility target alongside the existing 3.0.x line. The release notes do not state the minimum Laravel 13 minor version or whether older Laravel majors remain supported, so confirm the exact constraint in composer.json and the CI matrix. For a greenfield Laravel 13 app, prefer the 3.1.x line over adopting 3.0.7 first.
- Which Laravel versions does php-panel/laravel-admin support?
- The 3.0.x line is used on Laravel 11 and 12, and v3.1.0 adds a Laravel 13 compatibility target. The release notes are ambiguous about whether the constraint widens to ^11|^12|^13 or drops older majors, so inspect the package composer.json rather than assuming. Also verify which Laravel 13 minor was tested in CI if you standardise on a specific patch level.
- Is upgrading from php-panel/laravel-admin 3.0.7 to 3.1.0 safe?
- It is a routine minor bump with no documented breaking changes, so risk is low for most Laravel 11 and 12 deployments. Pin to ^3.1, run your test suite, and smoke-test admin authentication and CRUD flows. Pay particular attention to any application code that reads session flash payloads because 3.1.0 includes a behavioural correction to the flash payload shape.
- What changed in the php-panel/laravel-admin 3.1.0 session flash fix?
- v3.1.0 contains one narrow bug fix confined to the session flash payload shape, using a plain array for session flash. It should be transparent unless your code depended on the older flash encoding or inspected flashed data directly. Check custom middleware, controllers, and view composers that read flash payloads, and add a regression test around those paths during upgrade.
- Can php-panel/laravel-admin really build an admin panel in ten minutes?
- The ten-minute claim refers to scaffolding a back-office interface with CRUD screens, authentication, and customizable resources, not to finishing a production-ready admin surface. Expect to spend additional time on config publishing, migrations for admin tables, auth guard wiring, route registration, and the front-end asset build. Customising models, forms, and UI to your domain will take longer than the initial scaffold.
- How customizable are php-panel/laravel-admin resources, forms, and UI?
- The package is designed to scaffold admin dashboards while keeping control over models, forms, and UI, and it exposes customizable resources. Depending on the build, the admin surface uses standard Laravel layers such as routes, controllers, auth guards, Blade views, and potentially Livewire or Inertia. That makes it a reasonable fit for teams already fluent in Laravel conventions, Eloquent, policies, and middleware.
- What are the main production risks of using php-panel/laravel-admin?
- The dominant risk is framework coupling because admin packages hook into session, auth, and serialization internals, and the 3.1.0 session-flash fix is direct evidence of that exposure. Watch for version-range ambiguity, transitive Node or Vite asset constraints from the admin UI build, and ecosystem lag if other packages in your stack are not yet Laravel 13 ready. It fits best for internal-facing admin panels such as ops, support, and content moderation rather than a separately deployed SPA with distinct scaling or compliance needs.
- Does php-panel/laravel-admin work in an existing Laravel 11 or 12 application?
- Yes, existing 3.0.7 deployments on Laravel 11 or 12 can take a routine minor upgrade to 3.1.x. There are no documented breaking changes, but verify the composer.json constraint after the release because the notes do not confirm whether older majors remain supported. Run your tests and verify admin auth, CRUD, and session flash behaviour before deploying.
- What PHP version does php-panel/laravel-admin require?
- The provided release information does not state a PHP version requirement, so do not assume compatibility with your standardised PHP runtime. Inspect the package composer.json for the PHP constraint and confirm it matches your production and CI versions. If the constraint is missing or too broad, validate the package in a staging environment on your target PHP version before adoption.
Weaver
How can I help you explore Laravel packages today?