- Is rmzamora/news-bundle a Laravel package?
- No. Despite the Laravel/PHP framing in some listings, it is a fork of SonataNewsBundle, a Symfony bundle from the Sonata Project ecosystem. It wires a news/article content type into SonataAdminBundle, SonataBlockBundle, and Doctrine ORM. There is no Laravel service provider, Eloquent model, or Blade view in the package.
- Can I use rmzamora/news-bundle in a Laravel application?
- Technically you could pull it in with Composer, but you would have to run Symfony's service container, Doctrine ORM, and the Sonata admin and block stacks alongside Eloquent and Blade. That means a second framework runtime, separate DI conventions, and a second upgrade cadence. For a Laravel target the practical answer is no; reimplement the article model natively instead.
- How do I install rmzamora/news-bundle?
- There is no documented Packagist release, so installation is Composer from VCS at best, pointing at the GitHub repository and pinning an explicit commit. You also need to enable the bundle in a Symfony kernel and configure Doctrine plus the Sonata Admin and Block bundles. Expect to resolve a dependency graph that couples Sonata Admin, Sonata Block, Doctrine ORM, and a specific Symfony minor.
- Which Symfony, PHP, and Doctrine versions does rmzamora/news-bundle support?
- The constraints come from whatever upstream SonataNewsBundle release the fork was cut from, so check the composer.json in the repository before planning anything. Because the fork is archived, there is no evidence of PHP 8.x deprecation work, Doctrine DBAL 3 or ORM 3 adoption, or alignment with current Sonata majors. Treat any version support as frozen at the fork point.
- What features does rmzamora/news-bundle provide?
- It gives you a news or article content type persisted through Doctrine ORM, plus category handling and admin CRUD screens via SonataAdminBundle. Blocks for page composition come from SonataBlockBundle. In a Symfony/Sonata application that is an idiomatic, ready-made news section; in a Laravel app the same feature set is a small custom build.
- Is rmzamora/news-bundle actively maintained?
- No. It is a personal fork that is archived, with zero stars and zero dependents, so there is no security response, no versioning policy, and no CI signal. Zero dependents also means no field validation and no shared debugging cost. Plan on owning any fixes yourself if you adopt it.
- What should I use instead of rmzamora/news-bundle for a Laravel blog?
- Model the domain natively: articles with title, slug, body, status, published_at, and author, plus categories, tags, and media attachments. Pair that with a Filament or Nova admin resource for CRUD and publishing. That keeps you inside one framework and one ORM and is typically a few days of work.
- How does this fork compare with sonata-project/news-bundle?
- The fork adds nothing over upstream unless it contains a specific patch you need, and the assessment found no such justification. For a Symfony/Sonata codebase, prefer sonata-project/news-bundle at a version matching your Symfony LTS. Only fall back to the fork after diffing it and confirming you can carry it long term.
- How do I test rmzamora/news-bundle integration?
- Boot a Symfony kernel in a functional test with the bundle, Sonata Admin, and Doctrine registered, load fixtures, and exercise the article CRUD and block rendering paths. Pin the exact dependency set in CI so a resolution change fails loudly rather than silently. There are no published tests or CI signals from the fork itself, so your own suite is the only safety net.
- What are the production risks of adopting rmzamora/news-bundle?
- The main risk is abandonment: an archived fork gets no security patches, so check the pinned dependency set for known CVEs and confirm the license is preserved cleanly before distributing. You also inherit dependency resolution fragility and likely PHP 8.x deprecations in older Sonata and Doctrine code. Decide internally who owns the fork and what the exit plan is before committing.