- Is rz/news-bundle compatible with Laravel?
- No. It is a Symfony2-era bundle that extends SonataNewsBundle and assumes the Symfony kernel, service container, Doctrine ORM, Twig, and likely the Sonata admin and asset stack. There is no Laravel service provider, no facade, no publishable config, and no extra.laravel auto-discovery entry. Dropping it into a Laravel app gives you nothing at runtime.
- Is the Composer package name rz/news-bundle or rzproject/news-bundle?
- The two differ and you must verify which one actually resolves before any composer require attempt. Run composer show against both names in a throwaway project and inspect the resolved package's composer.json. Getting this wrong wastes a spike and can pull unexpected transitive dependencies.
- Which Symfony and PHP versions does rz/news-bundle support?
- It targets Symfony2-era APIs and depends on SonataNewsBundle, so it should be assumed incompatible with current Symfony and PHP 8.2+ until a spike proves otherwise. The meaningful unknowns are the PHP constraint, the Doctrine major version, and stale transitive constraints in the dependency graph. Time-box a test install in an isolated project rather than in your application.
- Is rz/news-bundle still maintained?
- No. The repository is archived with zero stars and zero dependents, meaning there are no PHP version bumps, no security response, and no downstream validation of correctness. Its 0.03 quality score is the honest signal; the higher opportunity score reflects an unfilled niche in news and content tooling, not the viability of this artifact.
- Does rz/news-bundle require SonataAdminBundle?
- Given its Sonata lineage, it very likely couples to Sonata's admin block and asset pipeline, though this needs confirming by auditing the bundle's admin classes and composer.json. Even if the entities load without it, bridging Symfony bundle conventions into Laravel is pure cost with no reuse. You would still write the service provider, container bindings, and Eloquent layer yourself.
- What does rz/news-bundle actually provide?
- It provides Doctrine-backed entities for news items, categories, and metadata, flexible routing for listing and detail pages, Twig templates ready for customization, event and service extension points, and simple configuration through a bundle extension. All of that is Symfony wiring except the domain shape. The only portable asset for a Laravel app is a news entity plus a repository with published and latest finders.
- Can I reuse the Doctrine entities and repositories in an Eloquent model?
- Only as a read-only specification, not as code. Treat the Entity and Repository directories plus any validation or routing config as the design input for a Laravel-native module. Map Doctrine types to Eloquent casts, ManyToOne relations to belongsTo, and repository finders to named scopes such as scopePublished and scopeLatest so controllers stay thin.
- How much work is porting rz/news-bundle to Laravel?
- Plan it as a port, not an install, measured in hours to days rather than an integration task. Audit the license, entities, finders, and config surface, extract the domain requirements including fields and draft/published/archived states, then implement natively with migrations, policies, factories, and tests in an internal namespace. A TPM should not schedule this as adding the package.
- What are the production risks of adding rz/news-bundle to a Laravel service?
- The technical risk is high and one-directional. Archived code gets no PHP version bumps, no security fixes, and no compatibility guarantees, and its stale transitive constraints will eventually break on a framework or language upgrade with no upstream to fix it. You would also be relying on an unvalidated artifact with no issue history to learn from.
- What should I use instead of rz/news-bundle for news and articles in Laravel?
- Rebuild the small slice you actually need natively, or evaluate a maintained Laravel-native content package. First decide which features are genuinely required, such as publishing state, categorization, archival, or feeds, and estimate the cost of building just those. Keep the abandoned bundle off any critical path and set an explicit build-versus-fork decision gate before committing engineering hours.