Weave Code
Cms Bundle Laravel Package
softspring/cms-bundle
Softspring CMS Bundle is a flexible content management bundle for Symfony apps, offering page management, reusable content blocks, menus, and an extensible admin interface to help teams build and maintain websites faster.
A cms bundle
Frequently asked questions about Cms Bundle
- Can I use Softspring CMS Bundle with Laravel?
- No. Softspring CMS Bundle is a Symfony bundle, not a Laravel package, and it will not install or boot under Laravel without a Symfony kernel and dependency injection container present. If your application runs Laravel, treat this as a no-fit and stop the evaluation. Confirm the consuming framework before doing any deeper compatibility work.
- How do I install Softspring CMS Bundle in a Symfony application?
- Install it with Composer, enable the bundle in your Symfony bundle configuration, and apply the bundle's required configuration for pages, blocks, menus, and SEO metadata. Check the bundle's composer.json for the exact Symfony and PHP constraints before updating. If the release touches admin assets, rebuild or republish those assets as part of the install. Run your application test suite and verify admin and front-end routing after activation.
- What content management features does Softspring CMS Bundle include?
- It provides reusable CMS building blocks: pages and content blocks for flexible content, tree-based menu management, and SEO metadata for titles, descriptions, and slugs. It uses Symfony-native entities, forms, and admin integration, and its architecture is extensible for custom content types. It is intended for teams that want editable site content without building a CMS from scratch.
- Which Symfony and PHP versions does Softspring CMS Bundle support?
- The changelog supplied does not verify a support matrix, so check the bundle's composer.json and CI configuration for the declared Symfony and PHP constraints. Do not assume Laravel or generic PHP compatibility from the package description. Confirm that your Symfony and PHP versions are actively tested before committing to the dependency.
- What changed in Softspring CMS Bundle v5.6.0?
- v5.6.0 is a minor release over v5.5.10 containing two backward-compatible changes. It fixes a modal transition race in the admin UI, which is a presentation-layer defect with no API surface change. It also adds support for disabled CMS sites, a functional enhancement to multi-site handling and the only change with potential behavioral impact. No schema migration or config rewrite is implied by the changelog.
- How do I upgrade Softspring CMS Bundle from v5.5.10 to v5.6.0?
- Bump the composer constraint, run composer update softspring/cms-bundle, rebuild admin assets if the bundle ships its own front-end build, and run your application test suite. The changelog implies no data migration for the v5.5.10 to v5.6.0 path. Add regression testing for multi-site resolution because disabled-site behavior is the only functional change. Teams on earlier majors should treat the upgrade as a separate planned migration.
- What does disabled CMS site support mean in Softspring CMS Bundle?
- It is a functional enhancement that lets the CMS handle sites marked as disabled in a multi-site setup. The exact semantics are not verified in the changelog: confirm the HTTP status, routing exclusion, admin visibility, and cache behavior. If your deployment currently simulates disabled sites with config workarounds, test routing, 404 handling, and sitemap output for existing enabled sites after upgrading.
- Is Softspring CMS Bundle production-ready for a Symfony app?
- Risk is low for the two v5.6.0 changes in isolation, but moderate-to-high for the dependency overall because key factors are unverified. Those include single-maintainer concentration, test coverage, CI posture, security disclosure process, Symfony/PHP support matrix, license terms, and commercial support options. Assign an internal owner and review those items before relying on the bundle in production.
- What are alternatives to Softspring CMS Bundle?
- Evaluate alternatives against your content model, admin UX, and multi-site topology rather than feature lists alone, because a CMS bundle is an opinionated and invasive dependency. This bundle typically owns routing, admin UI, Doctrine entities, and Twig templates, so fit depends on whether your conventions match. If they do not, compare other Symfony CMS bundles or a custom content model with a smaller surface area.
- How do I test Softspring CMS Bundle after upgrading?
- Run your application test suite after the Composer update, then add targeted regression tests for multi-site resolution, disabled-site routing, 404 handling, and sitemap output. Rebuild and smoke-test admin assets to confirm the modal transition fix and check for conflicts with local theme customizations. Also verify the composer constraint, Doctrine mapping, and any configuration changes before deploying. Ongoing maintenance should include tracking release cadence and upstream ownership.
Weaver
How can I help you explore Laravel packages today?