Weave Code
Sylius Happy Cms Plugin Laravel Package
agence-adeliom/sylius-happy-cms-plugin
Sylius plugin that integrates Happy CMS, letting store admins manage pages, content blocks, and rich text alongside commerce data so you can build flexible merchandising content without custom development.
CMS plugin for Sylius with a visual page builder in the admin: content blocks, live preview, media manager, menus, SEO and multilingual pages
Frequently asked questions about Sylius Happy Cms Plugin
- Can I use agence-adeliom/sylius-happy-cms-plugin in a Laravel application?
- No, not as a native Laravel package. It is a Sylius/Symfony plugin built on Symfony bundles, Sylius resources, and Doctrine ORM, with no Laravel service provider or Eloquent integration. It only fits a Laravel team as a separate Symfony service behind an API boundary.
- How do I integrate Happy CMS content into Laravel?
- Run Sylius with Happy CMS as its own Symfony application and expose pages, routes, and content blocks through HTTP/JSON or a content API. Laravel consumes that API for merchandising content; the integration cost sits in the API contract, auth, and deployment, not in the Composer package. Direct in-process use from Laravel is not feasible.
- What use cases does Happy CMS add to Sylius?
- It lets Sylius store admins manage pages, content blocks, and rich text alongside commerce data. Typical uses are flexible merchandising pages, reusable content blocks, and CMF-style routes without custom CMS development. It is aimed at Sylius storefronts, not Laravel content models.
- How do I install and configure sylius-happy-cms-plugin?
- Install it with Composer in a Sylius application and register the bundle using Sylius/Symfony bundle conventions. Configuration is handled through Sylius resources and Happy CMS routes and blocks rather than Laravel config files. Check the package README for the exact bundle class and required config because the supplied excerpt does not list them.
- Does v2.4.0 break CrudAdminFactory or generated admin classes?
- For code that extends or calls CrudAdminFactory, yes: PR #90 removes that factory and it is a dependency-API break, not a runtime-flagged deprecation. PR #91 also changes maker output so generated admin classes emit #[AsAdmin], which requires easy-crud 2.4+. Grep for CrudAdminFactory, upgrade easy-crud in isolation, and diff regenerated admin classes in a branch before merging.
- What easy-crud version does v2.4.0 require for new admin classes?
- Release notes indicate that newly scaffolded #[AsAdmin] admin classes require easy-crud 2.4+. The supplied material does not confirm whether composer.json declares ^2.4 or a wider constraint, so inspect it before upgrading. Consumers pinned below 2.4 can generate admin classes that fail to register.
- Is Symfony AI Mate a hard dependency in v2.4.0?
- PR #92 adds Symfony AI Mate tooling for CMF routes and blocks, and it is likely dev-only, but the release data does not confirm a require versus require-dev entry. Inspect composer.json and CI dependency resolution before production rollout. Treat it as an optional tooling dependency and a possible source of version conflicts.
- Which Sylius and PHP versions are supported by v2.4.0?
- The provided release assessment does not include a supported Sylius/PHP version matrix for v2.4.0. Check composer.json and the CI matrix before adoption, especially with the easy-crud 2.4+ requirement. Also confirm the maintainers' stated path to easy-crud 3.x.
- What are the maintenance and bus-factor risks of this plugin?
- Bus factor is a concern: all three recent PRs come from one author, and the release notes list that same author as a new contributor, suggesting automation rather than contributor growth. A minor release also carried a removed class and maker-output behavior change, so semver signals are weaker than the actual change. Pin versions, audit dependencies, and keep admin regeneration plus cache warm and container compile in CI.
- What are alternatives if I need CMS content in Laravel?
- For native Laravel content, evaluate Laravel CMS or content-model packages that use Eloquent and Blade/Livewire rather than adopting a Symfony plugin. If you need Sylius commerce plus CMS, keep Happy CMS inside Sylius and expose content to Laravel through an API. Do not treat this plugin as a drop-in Laravel library.
Weaver
How can I help you explore Laravel packages today?