Weave Code
Ckfinder Symfony2 Bundle Laravel Package
ckfinder/ckfinder-symfony2-bundle
Symfony bundle that integrates CKFinder, the file manager and browser for CKEditor, into Symfony 2 applications, letting you add upload, browsing, and file management features to your editor with minimal configuration.
CKFinder 3 bundle for Symfony 2
Frequently asked questions about Ckfinder Symfony2 Bundle
- Can I install ckfinder/ckfinder-symfony2-bundle in a Laravel application?
- No. This repository is a Symfony 2 bundle that provides dependency-injection glue, a configuration tree, service definitions and route loading for Symfony's kernel. Laravel has no Bundle concept or Extension class, so there is essentially no code you could reuse even if it installed. Composer will also refuse to resolve it alongside a supported Laravel release, because the bundle pins symfony/symfony to the 2.x line while Laravel 9, 10 and 11 require Symfony 6 or 7 components.
- Does this bundle work with Laravel 9, 10 or 11?
- No. The bundle constrains Symfony to the 2.x series, which reached end of life in November 2018, and it targets a PHP 7-era range. Every supported Laravel release depends on modern Symfony components, so dependency resolution fails outright. Forcing an install with --ignore-platform-reqs produces runtime signature and container errors rather than a working setup, so this is a hard stop rather than a configuration problem.
- What is the difference between a Symfony bundle and a Laravel package?
- A Symfony bundle plugs into Symfony's kernel through an Extension class, a compiler-pass-driven configuration tree, service definitions and route loaders. Laravel has no equivalent Bundle layer; packages register through a service provider, a publishable config file and explicit route files. Because almost all of this repository's code is Symfony-specific glue, none of it transfers to a Laravel package, which is why the repository is better treated as reference documentation than as a dependency.
- How do I integrate CKFinder 3 into a Laravel application?
- Target the CKFinder 3 PHP connector directly rather than the Symfony bundle. Build a thin Laravel adapter around it: a service provider that binds the connector configuration, a publishable config/ckfinder.php, and routes registered under an authenticated middleware group. Map authorization onto the connector's ACL hooks using Laravel gates or policies, then wire the front end into your editor.
- What settings should a Laravel CKFinder configuration file expose?
- The bundle's configuration tree is a useful checklist of what to expose, even though the code is not reusable. Expect to cover the connector's license settings, authentication and ACL callbacks, backend adapter and storage path (local disk, S3 or similar), upload size and MIME restrictions, thumbnails, and resource type definitions. In Laravel these belong in a publishable config/ckfinder.php bound through the service provider.
- Is CKFinder free to use in a Laravel project?
- No. CKFinder is commercial software, and production use carries a licensing obligation that is not visible in this repository's metadata. Before writing any integration code, confirm that you hold a license covering the version the PHP connector targets. That licensing cost is often the deciding factor when comparing CKFinder against a maintained open-source upload package.
- How do I connect CKFinder to CKEditor in Laravel?
- Route the editor's file browser requests to endpoints served by your Laravel adapter over the CKFinder 3 PHP connector. Register those routes in routes/web.php inside an authenticated middleware group rather than relying on the bundle's route loading. Then point the editor's file browser configuration at your route URL and verify the request, response and CSRF contract end to end in the browser.
- How should I test a CKFinder integration before going to production?
- Start by spiking the CKFinder 3 PHP connector standalone in a container with no framework, validating upload, browse, thumbnail and ACL behaviour on your target PHP version. Once that works, wrap it in the Laravel adapter and add feature tests covering upload validation, filename and path traversal handling, and endpoint authorization for unauthenticated and unauthorized users. Run a focused security review on those three areas before shipping.
- Is ckfinder/ckfinder-symfony2-bundle still maintained and safe for production?
- It is not a safe production dependency for a Laravel application. Symfony 2 has been end of life since November 2018, the repository shows zero stars and zero dependents, so there is no production evidence, issue history or third-party patching. Forking it means inheriting ownership of an abandoned Symfony integration with no upstream to merge from.
- What are the alternatives to this bundle for file management in Laravel?
- Most WYSIWYG editors have first-party or actively maintained Laravel upload and browsing packages, and those avoid the licensing and compatibility issues here. If you specifically need CKFinder, the defensible option is a small Laravel adapter built on the CKFinder 3 PHP connector. Decide first whether you need a full admin file manager or just an upload and browse endpoint for CKEditor, because that changes the build-versus-buy decision entirely.
Weaver
How can I help you explore Laravel packages today?