- Is rz/page-bundle a Laravel package?
- No. rz/page-bundle is a Symfony2 bundle, indicated by its rzproject namespace and -Bundle suffix, and it directly extends SonataPageBundle. It relies on Symfony kernel and bundle registration, service-container wiring, Doctrine ORM mappings, and Twig rendering. Laravel's container, routing kernel, Eloquent, and Blade are incompatible without a fork.
- Does rz/page-bundle work with Laravel 10 or 11?
- No. The package targets Symfony 2-era APIs and SonataPageBundle, so it cannot be installed or booted in a modern Laravel application. Laravel 10 and 11 use a different service container, routing kernel, ORM, and templating engine. There is no adapter layer, and the package is archived with zero dependents.
- How do I install rz/page-bundle?
- You would normally install it with Composer as rz/page-bundle, but the repository is archived and no longer maintained. Installation against a supported PHP 8.x runtime is not guaranteed and may fail dependency resolution. For a legacy Symfony 2 app that already vendors it, Composer may still resolve from an existing lock file.
- What Symfony versions does rz/page-bundle support?
- It is pinned to Symfony 2-era APIs because it is an extension of SonataPageBundle. It does not support Symfony 5.4, 6.x, or 7.x, and its legacy Doctrine and PHP constraints make modern resolution unlikely. That puts it several major versions behind any supported runtime.
- Is rz/page-bundle still maintained?
- No. The repository is archived, has zero stars and zero dependents, and shows a health score of 0.03. There is no evidence of tests, CI, or static analysis, and no CVE remediation path. Adopting it means forking and owning the code on day one.
- What are the best Laravel alternatives to rz/page-bundle for page management?
- For Laravel-native page management, build a small slice with a pages table, slug-based route resolution, an admin form via Filament or Nova, and Blade templates. If scope grows, consider Statamic, a Laravel-native flat-file CMS, or a headless CMS such as Sanity, Contentful, or Strapi. The core page, slug, metadata, and templating feature is roughly one to three engineer-days to reproduce.
- Can I use rz/page-bundle with SonataPageBundle?
- rz/page-bundle is itself a direct extension of SonataPageBundle, so it assumes SonataPageBundle is present and configured. That lineage also means it inherits SonataPageBundle's own maintenance trajectory and transitive dependencies. Check whether your SonataPageBundle version is maintained before considering a fork.
- Does rz/page-bundle include SEO fields for page titles and metadata?
- Yes, the package advertises SEO-ready fields for titles, descriptions, and metadata, along with slug-based routing and configurable template layouts. Those primitives are the genuinely useful part of the package as a feature checklist. However, they are easy to reproduce in Laravel using Eloquent fields and Blade meta tags.
- What are the production risks of using rz/page-bundle?
- The risks are high: archived package, no CVE remediation, Symfony 2 and legacy Doctrine compatibility, no tests or CI, and abandonment. Supply-chain and dependency-resolution failures are a matter of when, not if. For any active product surface, integration feasibility is effectively zero.
- How do I build a lightweight CMS for pages in Laravel without rz/page-bundle?
- Create a pages table with slug, title, description, metadata, and template fields, resolve routes by slug in a catch-all route, and render with Blade layouts. Add an admin resource via Filament or Nova for editing, and cache rendered pages for performance. This avoids the Symfony and Doctrine mismatch and keeps the feature Laravel-native.