Weave Code
Init Cms Bundle Laravel Package
networking/init-cms-bundle
Init CMS Bundle provides a modular PHP content-management foundation for rapid site building, including pages, navigation, media handling, and admin tooling that integrate cleanly and remain easy to customise. A practical starting point for developers who want CMS features without a heavy platform l...
the flexible cms core for symfony developers
Frequently asked questions about Init Cms Bundle
- How do I install networking/init-cms-bundle in a Laravel application?
- Install it with Composer using composer require networking/init-cms-bundle, then let Laravel's package discovery register the service provider and facade. Publish the package config with the vendor:publish command so you can set your content and media options, then run the migrations to create the page and media tables. Because version 6.4.14 requires PHP 8.2 or newer, confirm your local and CI runtimes match before you install.
- What PHP and Laravel versions does Init CMS Bundle support?
- The current release targets PHP 8.2 or higher, ideally 8.3, and a modern Laravel line such as Laravel 11 and above. It is not usable as a drop-in on PHP 8.0 or 8.1 applications. If your application is still on Laravel 9 or 10, treat the package upgrade as a platform upgrade project rather than a routine dependency bump.
- Why does a patch release like 6.4.14 contain breaking changes?
- The release is labelled 6.4.14 but ships explicit backward-incompatible changes, including attribute-based page definitions and serializer-driven page persistence. That means a caret constraint such as ^6.4 can pull a breaking change on a routine composer update. Pin the package to an exact version, commit your composer.lock, and enforce a lockfile gate in CI. Plan and communicate the upgrade as if it were a major version.
- How do I migrate page classes from docblock annotations to PHP 8 attributes?
- Page definitions are now expressed through PHP 8 attributes on classes instead of docblock annotations. The rewrite is mechanically bounded, so it can usually be handled with a Rector rule or a scripted rewrite across your page classes, followed by a review pass. Regenerate or clear any caches that store parsed metadata, and re-run your page rendering tests to confirm every page type still resolves. Do this on a dedicated upgrade branch so the change is easy to revert.
- Will my existing page records still load after the move to Symfony Serializer?
- This is the highest-risk part of the upgrade: delegating page payload persistence to Symfony Serializer likely changes how page data is stored, and legacy records may fail to deserialize or deserialize lossily. Take a full database backup and export all page records in their current serialized form before touching anything. Then test deserialization against real legacy records in a staging environment and prepare a one-time migration or backfill if needed. There is no stated migration path in the release notes, so verify before you deploy.
- Will the admin UI redesign break my custom fields, blocks or view overrides?
- The release includes an editor-facing UI redesign, which can break custom CSS, JavaScript, admin view overrides and acceptance tests that target the old markup. Extension points such as custom field types and block previews may also have shifted, so re-test each one against the new admin surface. Check the package documentation to confirm which extension points are documented as stable, and budget time for markup and screenshot comparisons. Customisations layered on the old admin UI are the least likely to survive unchanged.
- Do I need to configure the Symfony Serializer dependency?
- Yes. The package now pulls in symfony/serializer along with its normalizer and encoder configuration surface, and defaults are unlikely to match your content model. Make a deliberate decision about which normalizers and encoders are registered, and where your page payloads are stored and read back. Document that configuration so future upgrades do not silently change the serialized representation of your content.
- What is the rollback path if the upgrade goes wrong?
- Freeze the current package version explicitly in composer.json before starting, so a composer update cannot drift you onto the breaking release. Take a full database snapshot plus an export of all page records in their current serialized form, since that artifact is both your rollback point and the input to any backfill. If the upgrade fails, restore the snapshot and serve it with the previous package version, which is why isolating the platform upgrade from the package upgrade matters. Keep the upgrade on its own branch so reverting is a merge decision, not an archaeology exercise.
- How should I test the Init CMS Bundle upgrade in CI?
- Match your CI matrix exactly to the production runtime, including the PHP version, so drift between PHP 8.1 production and PHP 8.2 CI does not become a live failure mode. Enforce the Composer lockfile in the pipeline, and run deserialization tests against fixtures captured from real legacy page records. Add smoke tests for page rendering, navigation, media handling and the admin surface, including any custom field types or block previews you rely on. Ship the PHP and Laravel upgrade independently first and confirm the old package version still works before bumping it.
- Is Init CMS Bundle a good alternative to WordPress, Drupal or Statamic for a Laravel project?
- Init CMS Bundle is aimed at developers who want pages, navigation, media handling and admin tooling without the lock-in of a heavyweight platform, and it stays inside your Laravel codebase and Eloquent models. That suits teams that want to customise content structures in PHP and keep deployment as a normal Laravel release. Full platforms such as WordPress or Drupal bring more out-of-the-box editorial features but a very different extension and hosting model, while Laravel-native options like Statamic sit somewhere in between. Evaluate it against your need for long-term maintenance, upgrade discipline and how much editorial tooling you need on day one.
Weaver
How can I help you explore Laravel packages today?