- Is th3mouk/cms-page-bundle a Laravel package?
- No. It is a Symfony bundle that extends SonataPageBundle, so it relies on Symfony's bundle, dependency injection, and kernel model rather than Laravel service providers, facades, or Eloquent. There is no Laravel integration path, so it should not be evaluated as a Composer package for a Laravel application.
- Can I install th3mouk/cms-page-bundle in a Laravel project?
- You can run composer require, but it will not function as a Laravel CMS page layer because it requires Symfony HttpKernel, the DI bundle system, and SonataPageBundle. Expect dependency resolution conflicts with modern Laravel's Symfony 6/7 components. For a Laravel app, treat this package as out of scope.
- Which Laravel versions does th3mouk/cms-page-bundle support?
- None. The package has no Laravel service provider, config, routes, views, or migrations, and it does not target any Laravel version. It is built for Symfony applications running SonataPageBundle. Laravel teams should look at Filament, Statamic, or a simple pages table instead.
- What does th3mouk/cms-page-bundle actually do?
- It is a thin developer-ergonomics wrapper around SonataPageBundle that aims to simplify page creation, storage, and rendering for Symfony developers. It adds no standalone CMS capability; it depends on SonataPageBundle and typically SonataAdminBundle. The author's own description frames it as a simplification layer, not a new feature set.
- Is th3mouk/cms-page-bundle still maintained?
- No. The repository is archived, has one star, zero dependents, and no visible CI, releases, or version matrix. Upstream maintenance is effectively zero, so any future fixes would be your responsibility. That makes it a supply-chain risk even in a Symfony codebase.
- What Symfony and Sonata versions does th3mouk/cms-page-bundle require?
- Expect EOL pins such as Symfony 2.8/3.x, Sonata 3.x, and PHP 5.x/7.0-era constraints, though you should verify by resolving it in a scratch project and reading the lockfile. It is unlikely to install cleanly on PHP 8.2+ with Symfony 6 or 7 without patching. Run composer why-not against your constraint set before considering it.
- What are good alternatives to th3mouk/cms-page-bundle for Laravel?
- For Laravel, use Statamic for a full CMS, Filament with a simple pages resource, or a hand-rolled pages table with Blade views. For Symfony, evaluate stock SonataPageBundle, Symfony CMF, or a headless CMS instead. A one-to-three day internal page layer often replaces this wrapper entirely.
- How do I test th3mouk/cms-page-bundle before adopting it?
- Run a one-day timeboxed spike in a throwaway Symfony branch: allow the abandoned package in Composer, boot a minimal kernel, and confirm SonataPageBundle compatibility with a working page render. Do not rely on code reading alone. In a Laravel app, no spike is warranted because the architecture does not fit.
- Can I use th3mouk/cms-page-bundle in production?
- Not recommended. It is archived, single-maintainer, and pins an EOL Symfony/Sonata stack, which creates an upgrade deadlock and no upstream CVE response path. If you must adopt it, fork it under MIT, pin a commit SHA, vendor it internally, and register a named owner and review cadence. The default recommendation is not to adopt.
- How is th3mouk/cms-page-bundle different from SonataPageBundle?
- It does not replace SonataPageBundle; it sits on top of it as an ergonomic simplification for developers. You still need SonataPageBundle and often SonataAdminBundle installed and configured. If you want the underlying capability, start with SonataPageBundle directly and decide whether the wrapper saves enough time to justify an abandoned dependency.