Weave Code
Advanced Content Bundle Laravel Package
sherlockode/advanced-content-bundle
Advanced Content Bundle is a Symfony bundle for building flexible, editable content pages. It provides reusable content blocks, configurable block types, and a structured content model that lets developers add dynamic CMS features to Symfony applications.
Symfony Bundle for CMS content with custom fields
Frequently asked questions about Advanced Content Bundle
- Is sherlockode/advanced-content-bundle a Laravel package?
- No. SherlockodeAdvancedContentBundle is a Symfony bundle, not a Laravel package. Using it in Laravel would mean adding Doctrine ORM, the Symfony Doctrine event bridge, and Twig alongside Blade and Eloquent, creating a dual-ORM and dual-templating architecture that is expensive to own. Confirm the target framework before evaluating it further.
- How do I install Advanced Content Bundle in a Symfony application?
- Install it with Composer, register the bundle in config/bundles.php, add bundle configuration, and make sure Doctrine and Twig wiring are in place. For v0.10.0, plan for Symfony 7.4, Doctrine ORM 3, Twig 3, and PHP 8.2+ based on the migration notes. Always read the package's composer.json constraints directly before committing.
- Which Symfony versions are supported by v0.10.0?
- The v0.10.0 notes reference a Symfony 7.4 migration, which implies a raised minimum version. Applications on Symfony 6.4 LTS or 7.0 through 7.3 should assume they are dropped or untested until the composer.json constraints are verified. Run composer why-not sherlockode/advanced-content-bundle 0.10.0 in the target app to surface conflicts.
- Does it work with Doctrine ORM 3?
- v0.10.0 includes Doctrine ORM 3 event listener compatibility work, so ORM 3 is the intended target. This is also the highest-risk area because a listener signature mismatch can fail silently, meaning lifecycle hooks simply stop firing and content side effects quietly stop. Confirm whether your app uses ORM 2 or ORM 3, since that single fact likely determines whether the upgrade is drop-in or a paired migration.
- How do I define custom content types and dynamic fields?
- The bundle lets you define content types with custom fields and manage structured content entries in the admin. That makes it suitable for CMS pages, articles, and editorial blocks without hard-coding layouts. The architecture is Doctrine-backed and extensible, so you can adapt the content model to your application's needs.
- How do I render reusable content blocks in Twig?
- The bundle provides reusable content rendering in Twig templates, so pages and blocks can be composed from structured content rather than hard-coded layouts. v0.10.0 includes a Twig extension fix that changes how the extension is invoked, and this can alter rendered output for existing templates. Review any templates that call the extension in the old pattern before upgrading.
- Is there an admin CRUD interface for content entries?
- Yes. The bundle provides admin-friendly CRUD for content entries, letting editors manage structured content without developer involvement. Combined with configurable content types and dynamic fields, this supports CMS-style editorial workflows for pages, articles, and blocks.
- What are the upgrade risks from 0.9.9 to 0.10.0?
- v0.10.0 is pre-1.0, so SemVer stability guarantees do not apply and a minor bump may contain breaking changes. The release combines a Rector full-rules refactor, a Symfony 7.4 migration, Doctrine ORM 3 listener changes, strict type fixes, and a Twig extension fix, and the notes contain no explicit breaking changes section. Ask the maintainer for a documented BC-break list, a CHANGELOG or UPGRADE guide, the CI matrix, and whether the behavioural test suite was updated alongside the Rector pass.
- What are alternatives to Advanced Content Bundle for Symfony CMS content?
- Alternatives include Symfony CMF, Sulu, Ibexa, or building custom Doctrine entities and admin CRUD with EasyAdmin or Sonata. This bundle is a lighter-weight option focused on configurable content types, reusable blocks, and Twig rendering. For Laravel projects, look at Laravel-native CMS packages instead, because this bundle is Symfony-only.
- How actively is the package maintained and is a 1.0 release planned?
- The v0.10.0 work is largely correctness and compatibility maintenance, including CS Fixer, Rector, strict types, Twig extension fixes, Doctrine ORM 3 listeners, and Symfony 7.4 migration, which shows the package is being brought forward. It is still at 0.x, and there is no documented 1.0.0 or LTS commitment in the provided notes. Ask the maintainer about the release gating CI matrix and plans for a stable major version.
Weaver
How can I help you explore Laravel packages today?