- Is rz/block-bundle a Laravel package?
- No. The repository is a Symfony2-era bundle, indicated by the vendor name, the Bundle suffix, and its Resources/config layout. It relies on Symfony bundle wiring and does not provide a Laravel service provider or package auto-discovery. The overview's Laravel framing is misleading; treat the block, zone, and renderer concept as framework-agnostic prior art rather than a Laravel dependency.
- How do I install rz/block-bundle in a Laravel app?
- You should not install it as a Laravel dependency. There is no Laravel service provider, no publishable Laravel config, and no Composer auto-discovery path that would register its Symfony bundle wiring in a Laravel application. The practical approach is to read the block-resolution logic and reimplement the pattern in a small internal package with a Laravel service provider, config file, and Blade renderers.
- Does rz/block-bundle support Laravel 10 or Laravel 11?
- No. It predates modern Laravel and is built around Symfony bundle conventions rather than Laravel's service container and package discovery. The repository is archived, so there is no path to Laravel 10 or 11 support. Any integration would require a fork or a native reimplementation.
- Which PHP and Symfony versions does rz/block-bundle require?
- The exact constraints should be read from composer.json before any use, but the bundle is Symfony2-era and plausibly targets older PHP and Symfony branches. That likely means incompatibility with PHP 8.2+ and current Symfony or Laravel runtimes. Because the repository is archived, there is no upstream patch path for deprecations or runtime failures.
- Is rz/block-bundle still maintained?
- No. The repository is archived, which makes it read-only: no security patching, no PHP version support, no bug fixes, and no issue triage. It also shows zero stars, zero dependents, and no visible CI matrix or release cadence. An archived repo is not a viable dependency for a production Laravel application.
- What license does rz/block-bundle use?
- The license must be verified directly in the repository before you copy, vendor, or reimplement any code. Archived repositories frequently omit licensing metadata or inherit ambiguous terms. Do not reuse the source until the license clearly permits forking and internal redistribution.
- Can I use rz/block-bundle with Laravel Eloquent instead of Doctrine?
- Not without a fork. The bundle likely couples block storage to Doctrine ORM entities and RZ Project's schema, and its Symfony wiring assumes the Doctrine persistence layer. Laravel uses Eloquent, so the storage layer would need to be rebuilt. If you only want the abstraction, extract the block type, zone placement, ordering, and visibility model and persist it with Eloquent.
- How does the block and zone abstraction work?
- The underlying model is framework-agnostic: typed, reusable content blocks are assigned to named zones, and tagged block-type services render them. Block types define fields and views, while zones act as string-discriminated regions for placement and ordering. That pattern can map to Laravel as a block-type registry contract plus Blade renderers, but the original Symfony implementation does not transfer directly.
- What are good alternatives to rz/block-bundle for Laravel?
- For Laravel, look at native content-composition approaches first: a block-type registry contract, Eloquent models for block instances, and Blade components for rendering. If you need a package, evaluate maintained Laravel page-builder or content-block packages with recent releases, CI, and Laravel version support. The key test is whether the package exposes a Laravel service provider, publishable config, and Blade-based rendering.
- Is rz/block-bundle safe for production?
- No. It is archived, has no upstream security response, no known production users, and no visible maintenance. For any component touching editorial or user-generated content, that lack of security patching is disqualifying. Use it only as a reference implementation, and only after verifying the license and extracting the pattern into code you own.