- Can I install fsi/admin-news-bundle in a Laravel application?
- No. fsi/admin-news-bundle is a Symfony bundle, not a Laravel package. It boots through Symfony's kernel and is registered in AppKernel, and Laravel does not implement the bundle contract even though it borrows many Symfony components. Composer resolution will typically fail before any code runs because its PHP 5.4 to 7.x and Symfony 2.x constraints conflict with a modern Laravel 10 or 11 stack.
- Does fsi/admin-news-bundle have a Laravel service provider or facade?
- It has no Laravel service provider, no Laravel-shaped config file, no facade, and no publishable assets in the Laravel sense. It relies on Symfony's DI extension and compiler-pass model for configuration. Any Laravel integration would require rewriting the package, not configuring it.
- What PHP and Symfony versions does fsi/admin-news-bundle support?
- The bundle targets the 2015-era stack: PHP 5.4 through 7.x, Symfony 2.x, and Doctrine 2.x. Running it requires a Symfony 2.8 or Symfony 3 host, and Symfony 2.8 has been end-of-life since November 2018. It is not compatible with PHP 8.1+ or Symfony 6 and 7 components used by current Laravel releases.
- Is fsi/admin-news-bundle still maintained?
- No. The last release was on 2015-03-12, and the repository has zero stars and zero dependents. There are no forks, issue triage, CVE monitoring, or community answers to rely on. The MIT license is effectively the only clean item in the package.
- What dependencies does fsi/admin-news-bundle pull into a project?
- It depends on a cluster of sibling and third-party bundles, including FsiAdminBundle for the admin shell, FsiMediaBundle for uploads and galleries, FsiDoctrineExtensionsBundle for translatable and tree behavior, plus KnpPaginatorBundle and Twig view inheritance. Those dependencies pin old Doctrine and Symfony versions, which is the direct cause of Composer conflicts in modern applications. The bundle also assumes era-appropriate front-end assets such as TinyMCE 4.x.
- Can I run fsi/admin-news-bundle headless or as an API behind Laravel?
- No. There is no HTTP-layer-only or headless mode. The news module ships as Doctrine entities, admin controllers, and Twig templates that all assume the host Symfony kernel and admin layout. You cannot salvage just the data layer without porting it by hand.
- Does fsi/admin-news-bundle support categories, translations, and scheduled publishing?
- Within its Symfony context, yes. It provides CRUD for news entries, category and tag organization, translatable entities through FsiDoctrineExtensionsBundle, media gallery attachments, and draft versus live publishing controls. Those features are the useful part of the package and are worth copying as a specification, but they are not portable as code.
- How do I migrate the news schema from fsi/admin-news-bundle to Laravel?
- Treat the repository as a design document rather than a dependency. Read the entities and controllers, then extract the schema by hand: News, NewsTranslation, NewsCategory, NewsCategoryTranslation, and the media join tables. Re-express that in Laravel migrations and Eloquent models, use spatie/laravel-translatable or per-locale tables for translations, spatie/laravel-medialibrary for media, and a published_at scope plus scheduler for publication windows. A one to two day discovery spike is usually enough to confirm whether any existing content also needs migrating.
- What Laravel alternative should I use instead of fsi/admin-news-bundle?
- There is no drop-in Laravel equivalent of this specific bundle. The common choices are a native Laravel build using migrations, Eloquent, spatie/laravel-translatable, and spatie/laravel-medialibrary, a module for an existing admin panel such as Filament, Nova, or Backpack, or a full CMS like Statamic or Craft. For a single news CRUD module, a native build is typically three to five days of work and avoids a second runtime.
- Is fsi/admin-news-bundle secure enough for production?
- No, the technical risk is high. The package has been unmaintained since 2015, and it carries known stored-XSS and upload-handling exposure through TinyMCE 4.x, hardcoded web/uploads paths, and annotation-mapped translatable entities that will never be patched. Adopting it also means hosting and securing an end-of-life Symfony 2.8 or Symfony 3 runtime indefinitely. For a Laravel application, that doubles the operational surface for one CRUD module.