- How do I install mafftor/laravel-file-manager in a Laravel application?
- Install it with Composer by running composer require mafftor/laravel-file-manager, then publish the package config and assets if the documentation instructs you to. Depending on your Laravel version, you may also need to register the service provider or run install commands. Set your storage disk and upload paths, expose the file manager routes, and verify the integration on a non-production branch before shipping.
- Which Laravel and PHP versions does mafftor/laravel-file-manager support?
- The repository's README and composer.json are the authoritative source for supported Laravel and PHP versions, so check them before adopting. The v2.0.12 release only changed the intervention/image constraint and did not expand tested framework coverage. Confirm your Laravel and PHP combination against the package's CI matrix or test it directly in a branch.
- Does laravel-file-manager support CKEditor, TinyMCE, and Summernote integrations?
- Yes, the package is described as a media gallery with CKEditor, TinyMCE, and Summernote support. That means you can wire the file manager as the file or image picker for those editors using their standard integration hooks. Take the exact configuration snippets from the package documentation, since editor plugin options and callback URLs vary.
- How do I configure storage disks and upload paths for the Laravel file manager?
- Configuration is typically handled through a published config file where you define the disk, base directory, and upload rules. Make sure the disk matches your application's filesystem configuration and that permissions, public URLs, and thumbnail paths are correct. Test with the same driver you use in production, because local and cloud drivers behave differently for visibility and URL generation.
- Does mafftor/laravel-file-manager work with intervention/image v2 and v3?
- Release v2.0.12 broadens the composer.json requirement to support intervention/image 2 and higher, but that does not guarantee full runtime compatibility with v3, which introduced API changes. Check the exact Composer constraint and the package's CI coverage, then exercise your own upload, resize, and thumbnail paths. If you depend on v3-only behavior, test carefully before pinning the package.
- How do I secure file manager routes and restrict uploads by user permissions?
- Restrict the file manager routes with Laravel middleware such as auth plus any role or permission checks your application already uses. Review the package's authorization hooks and validate uploads server-side for MIME type, size, and extension. Also limit which storage paths the manager can access so users cannot browse outside the intended directories.
- How do I test file uploads, browsing, and deletion in the Laravel file manager?
- Cover the core flows: browsing, upload, rename, delete, thumbnail generation, and authorization checks for users who should not have access. Use Laravel's filesystem fakes or a temporary local disk so tests never touch production storage. Include an assertion that the intervention/image version resolved in your lock file still supports the image transformations the package performs.
- Can I use laravel-file-manager with S3 or cloud filesystems like DigitalOcean Spaces?
- It should work with any Laravel filesystem disk, including S3 and S3-compatible services, provided the package is configured to use that disk and URLs are generated correctly. Cloud drivers introduce differences in visibility, signed URLs, and streaming that are worth validating in staging. Check the repository's issue tracker for known storage-driver caveats before relying on it in production.
- Is mafftor/laravel-file-manager maintained, and how do I upgrade from v2.0.11 to v2.0.12?
- Treat v2.0.12 as a patch-level update from v2.0.11: update the package in a branch, regenerate the lock file, and confirm the resolved intervention/image major version. Run Composer validation and your upload and thumbnail tests before merging. Review the repository's release history and open issues for maintenance signals and any documented upgrade notes.
- What are the alternatives to mafftor/laravel-file-manager?
- Alternatives include UniSharp/laravel-filemanager and other Laravel file manager packages, or building a smaller upload and media-picker layer yourself. Compare them on Laravel version support, editor integrations, storage driver coverage, authorization model, and maintenance activity. The right choice depends on whether you need a full browsing UI or just upload and picker endpoints.