- What is dcblogdev/laravel-admintw and what features does it provide?
- AdminTW is a Laravel admin UI and theme package that provides a ready-made back-office panel built with Tailwind CSS. It includes authentication, user, role and permission management, and a module generator for scaffolding CRUD screens. It is intended for Laravel applications that need rapid admin scaffolding without building a custom UI layer.
- How do I install dcblogdev/laravel-admintw in a Laravel app?
- Install the package with Composer, then publish its configuration, assets, and views as documented by the package. Laravel service provider discovery should handle the package registration. Follow the README for any required migrations, authentication setup, and asset publishing steps.
- Which Laravel and PHP versions are supported by v6.0.3?
- The release context provided does not list the exact Laravel and PHP constraints for v6.0.3. Check the package composer.json and repository before upgrading, then confirm your application meets those constraints in a development branch. This is especially important if you are upgrading from an older AdminTW release.
- Does laravel-admintw require Livewire or the TALL stack?
- AdminTW is described as a Laravel Livewire starter kit and TALL admin theme, so it targets Laravel applications using Blade, Tailwind CSS, and Livewire-oriented tooling. Confirm the exact frontend and build dependencies in composer.json and the package documentation. It is best suited to internal admin and back-office surfaces rather than customer-facing UI.
- How do I safely upgrade an existing app to v6.0.3?
- Work on a branch, pin your current version, and update Composer to v6.0.3. Republish assets, views, and configuration, then diff any locally overridden published files against the new versions. Specifically validate CKEditor image upload, modal close behavior, dynamic select behavior, and the 403 error page before deploying.
- What changed with CKEditor v5 and image upload in v6.0.3?
- The most material change in v6.0.3 is the switch to CKEditor v5 with image upload support. That change can require asset republishing, upload endpoint and storage configuration, CSRF handling, and file validation. It also has security and CSP implications beyond a routine patch update.
- How do I secure CKEditor image uploads in an admin panel?
- Protect upload endpoints with authentication and authorization middleware, and ensure CSRF handling is correct. Validate file type and size, use a dedicated storage disk, and review CSP rules for CKEditor v5. Also define retention and media-processing policies so uploads do not create unbounded storage or bandwidth load.
- Are there breaking changes in v6.0.3?
- The release notes do not state breaking changes for v6.0.3, and the patch-level fixes and PHPStan cleanup are low risk. However, published view and asset overrides can obscure upstream changes, so regression-test modal close events, dynamic select JavaScript, the 403 layout, and CKEditor uploads. Treat custom overrides as the main upgrade risk.
- How do I customize or override AdminTW views and assets without losing changes?
- Publish the package views, assets, and configuration, then inventory every file you override. On each upgrade, republish and diff your overrides against the upstream versions before merging changes. Avoid editing vendor files directly, and update custom overrides only after reviewing the release changes.
- Is laravel-admintw actively maintained and what support is available?
- The package has an active maintainer and frequent patch releases, and recent PHPStan fixes indicate attention to static analysis quality. It remains a single-maintainer dependency, so your team should own custom overrides, CKEditor configuration, and upload security validation. Support is primarily through GitHub issues and pull requests, with no commercial SLA indicated.