- Can I install koala/content-bundle in a Laravel application?
- No. It is a Symfony 2 bundle that depends on symfony/* ^2.3 components, while Laravel 9 and later require Symfony 6 or 7 components. Composer dependency resolution will fail before any Laravel code can use it. There is no Laravel service provider, facade, or Blade integration to install.
- What Laravel versions does koala/content-bundle support?
- None. Laravel 9 requires symfony/* ^6.0, Laravel 10 requires ^6.3, and Laravel 11 requires ^7.0, but the bundle pins Symfony ^2.3. That conflict blocks installation on every modern Laravel release. It was built for Symfony 2 applications, not Laravel.
- What is koala/content-bundle used for?
- It is a Symfony bundle for structured, editable content such as pages, reusable blocks, and custom content types. It adds routing, controllers, Doctrine entities, and Twig helpers so content can be managed separately from application code. It also includes admin-oriented workflows for editing that content.
- Is koala/content-bundle maintained, and does it support PHP 8?
- No. The repository is archived, has roughly 10 stars and zero dependents, and shows no PHP 8 work or security response. It targets Symfony 2.3/2.8, and Symfony 2.8 reached end of life in November 2018. Treat it as historical reference code, not a maintained dependency.
- How is koala/content-bundle configured?
- It is configured as a Symfony bundle using a Bundle subclass, a dependency-injection extension, and services.yml wiring. Routing is annotation-based, persistence uses Doctrine entities, and rendering uses Twig templates. None of those configuration mechanisms map onto Laravel's service providers, Eloquent, or Blade.
- Can I use koala/content-bundle for inline or WYSIWYG content editing?
- Only as prior art. The bundle's editing layer is tied to Mercury Editor, a jQuery/contenteditable/Rangy-era project effectively abandoned since around 2013. It is not a viable inline-editing component for a modern Laravel app. For new work, use a maintained editor such as TipTap, Editor.js, or ProseMirror.
- What are Laravel alternatives to koala/content-bundle?
- For a full CMS, evaluate Statamic, Filament, or Wink. For a narrow editing surface bolted onto an existing Laravel app, build Blade components with TipTap, Editor.js, or ProseMirror and store content in Eloquent models. Add server-side HTML purification before saving.
- Is koala/content-bundle safe for production?
- No. It is archived, unmaintained, and has no security response process, and its contenteditable HTML pipeline likely creates a stored-XSS surface. The underlying Symfony 2 framework has been unsupported since 2018. Do not run it in production; if you borrow ideas, add server-side purification such as mews/purifier.
- How do I migrate content from koala/content-bundle to Laravel?
- There is no automated migration path. Export the Doctrine-backed content records, map them to new Eloquent models and migrations, and design schema for content regions, revisions, and an audit trail rather than copying the Doctrine mapping. Run a requirements spike first and sanitize all imported HTML.
- Can I test koala/content-bundle in a Laravel test suite?
- No. Composer resolution fails before the package can be autoloaded in a Laravel project, so there is no integration surface to test. You cannot meaningfully exercise its routing, controllers, or Twig rendering inside Laravel's test harness. If you are evaluating the pattern, read the code and rebuild the pieces as Laravel-native tests.