- Is jonlil/ckfinder-bundle a Laravel package?
- No. It is a Symfony bundle that wires CKFinder's PHP connector into Symfony routing, controllers, dependency injection, and asset publishing. It does not provide a Laravel service provider, config publishing, or Laravel filesystem integration. Treat it as a Symfony 2-era package, not a Laravel Composer dependency.
- Can I install jonlil/ckfinder-bundle in a Laravel application?
- There is no supported integration path. The bundle depends on Symfony bundle conventions and targets PHP 5.3-5.6 era stacks, so installing it in Laravel 10/11/12 on PHP 8.2+ is expected to fail. The realistic path is to replace it, not port it, using CKFinder's connector directly or a Laravel-native file manager.
- What does jonlil/ckfinder-bundle do?
- It exposes CKFinder's PHP connector through a configurable Symfony route and controller, with bundle-level settings for upload paths, license, and connector options. It also helps publish CKFinder's frontend assets for Symfony apps. The package itself is Symfony glue, not a file manager implementation.
- Which Laravel versions and PHP versions does this package support?
- None are supported for Laravel; the bundle has no Laravel service provider or framework contracts. It is built around Symfony 2-era conventions and PHP 5.3-5.6 assumptions, with no upgrade path documented. Modern Laravel on PHP 8.2+ should be treated as incompatible.
- How do I configure CKFinder upload paths and a license in Laravel?
- You cannot do that through this bundle in Laravel because its configuration surface is Symfony bundle config. If CKFinder is required, use CKSource's current PHP connector directly and map upload paths to Laravel filesystem disks in your own config. A valid CKFinder commercial license must be on record separately.
- Is CKFinder free, or do I need a commercial license?
- CKFinder is commercial software from CKSource, so using it through this wrapper still requires an appropriate license. The bundle does not remove that procurement or compliance obligation. Confirm the licensed major version before planning any integration.
- What are the best Laravel alternatives to this Symfony CKFinder bundle?
- For most Laravel apps, use a maintained Laravel-native media library or file manager, or the uploader already built into your WYSIWYG editor. If CKFinder specifically is mandatory, integrate CKSource's connector directly and wire it to Laravel disks, auth middleware, and validation. Avoid the abandoned Symfony bundle as a middle layer.
- Can I use CKFinder's PHP connector directly in Laravel without this bundle?
- Yes. CKFinder's vendor-supported connector can be added as a Composer dependency and wired to Laravel's filesystem disks, routes, and auth middleware in-house. That gives you supported CKFinder code while dropping the abandoned Symfony glue. You still need a CKFinder license and careful upload security controls.
- Is jonlil/ckfinder-bundle maintained and safe for production?
- It shows no adoption signal, zero stars and dependents, and no apparent maintainer activity, so security fixes and upgrades are unlikely. Its job is to expose a file upload and browse endpoint, which is a high-risk attack surface, especially around an EOL CKFinder version. Do not put it into production without a formal risk review and a replacement plan.
- How should I migrate an existing CKFinder integration from Symfony to Laravel?
- Confirm the CKFinder license and major version, inventory existing assets and retention requirements, and define the actual capability needed: editor image insertion, DAM-style browsing, or end-user file management. Then replace the bundle by integrating CKSource's connector directly or choosing a Laravel-native file manager. Test PHP 8.x compatibility, authorization, MIME validation, and storage placement before migration.