Weave Code
Core Bundle Laravel Package
unite-cms/core-bundle
Unite CMS CoreBundle is the foundational Symfony bundle for the Unite CMS headless content management system. It provides core services, configuration, and integration points for managing structured content, building custom APIs, and supporting extensible admin workflows.
Core functionality for unite cms
Frequently asked questions about Core Bundle
- Can I install unite-cms/core-bundle in a Laravel application?
- Composer may install the package, but it is a Symfony bundle rather than a Laravel package. It expects Symfony's dependency injection container, bundle registration in config/bundles.php, the Symfony event dispatcher, security voters, and Doctrine's Symfony bridge. Putting it inside Laravel means building a Symfony-within-Laravel compatibility shell, so direct adoption is not recommended.
- Does Unite CMS CoreBundle support Laravel 10 or Laravel 11?
- No. There is no Laravel support by design because the bundle is built for Symfony. Laravel's service container, provider model, event system, and persistence conventions are different enough that a successful Composer install does not mean the package is supported. Use a separate Symfony service or a Laravel-native content layer instead.
- How do I integrate Unite CMS with Laravel?
- The defensible path is to run Unite CMS as a standalone Symfony/PHP service or container that exposes its generated GraphQL API, with Laravel acting as the client and orchestrator. Keep authentication, identity, and business workflows in Laravel, and make persistence boundaries explicit so the CMS owns content while Laravel owns everything else. Avoid in-process integration; if you must attempt it, hide Unite CMS types and services behind an adapter interface.
- Is unite-cms/core-bundle still maintained?
- There is no meaningful maintenance signal. The last tagged release was January 2020, the repository has near-zero stars and zero dependents, and the package score is effectively zero. That implies no upstream security patching, no compatibility work for current PHP or Symfony versions, no community support, and a single-maintainer bus factor. Adopting it means owning fork maintenance.
- What Symfony and PHP versions does Unite CMS CoreBundle require?
- The bundle targets a Symfony 4.4-era stack and should be expected to cause friction on PHP 8.x and modern Symfony versions. Verify exact Composer constraints against your target runtime before committing roadmap capacity. Pin a specific validated commit rather than floating on the 2020 tag, and run composer why-not to confirm compatibility.
- Can I use Unite CMS as a headless GraphQL CMS behind Laravel?
- Yes, that is the recommended architecture if Unite CMS is genuinely required. Run it as a standalone Symfony/PHP sidecar that exposes the GraphQL API generated from your content schema, and let Laravel call that API as a client. This keeps Symfony assumptions out of Laravel domain code and lets you isolate content data from identity and customer data.
- What are the alternatives to unite-cms/core-bundle for Laravel?
- The context does not provide specific alternative packages, but the practical options are a Laravel-native headless CMS or content layer, or a separate headless CMS service integrated over GraphQL. You can also use this repository purely as a reference for content-type, field-type, and permission modeling while building a thin Laravel-native layer. Avoid positioning a Symfony bundle as a Laravel dependency.
- How should I test Unite CMS CoreBundle before adopting it?
- Start with a time-boxed discovery spike rather than an integration epic. Stand up a clean Symfony 4.4-era skeleton, register the bundle, create one domain and one trivial content type, seed one record, and read it back over GraphQL. That single loop validates domain resolution, content type, field type, schema generation, and resolver wiring before you evaluate sidecar API integration from Laravel.
- Is Unite CMS CoreBundle safe for production use?
- Technical risk is high for a Laravel roadmap. The last release is from January 2020, there is no upstream security patching or current framework compatibility work, and the bundle is a fundamental framework mismatch for Laravel. Production use would require a named fork owner, a security-review and patch SLA, pinned commits, and isolation so the CMS never holds PII or identity data.
- Does unite-cms/core-bundle work with PHP 8?
- Expect friction on PHP 8.x because the bundle's last tagged release is from January 2020 and targets a Symfony 4.4-era stack. Check Composer constraints with composer why-not against your target runtime and validate a pinned commit in a spike. A successful install is the start of testing, not proof of PHP 8 compatibility.
Weaver
How can I help you explore Laravel packages today?