- Is fsi/gallery-bundle compatible with Laravel?
- No. It is a Symfony2 bundle registered through AppKernel and built on Symfony's DependencyInjection, Twig, routing, and form components. Laravel has no bundle registration lifecycle or Symfony DI semantics, so it cannot be dropped in as a dependency. The only realistic use in a Laravel project is as a reference implementation.
- Can I install fsi/gallery-bundle in a Laravel project with Composer?
- Composer may resolve it in isolation, but Laravel projects on PHP 8.1+ typically conflict with the bundle's Symfony 2.x and PHP ~5.3|~5.4 requirements. Even if installed, its service definitions and Twig templates will not boot in Laravel. Treat installation as unsupported.
- What Symfony and PHP versions does fsi/gallery-bundle require?
- The last release was 2015-03-10 and targets Symfony 2.x and the PHP 5.x era, with composer constraints around php ~5.3|~5.4. Symfony 2 reached end of life in 2019 and conflicts with modern PHP and Laravel 10/11. Do not expect compatibility with current Laravel versions.
- Is fsi/gallery-bundle still maintained or safe for production?
- No. There has been no upstream patching for roughly a decade, with 5 stars, 0 dependents, and no maintainer response path. Any transitive dependency it pins is likely unmaintained, and you would inherit full ownership on day one. The technical risk is high and largely irreducible.
- What is the best Laravel alternative to fsi/gallery-bundle for photo galleries?
- Use spatie/laravel-medialibrary for media collections and intervention/image for derivative generation. They support modern Laravel and PHP, are actively maintained, and cover uploads, thumbnails, conversions, and ordering. Effort is days rather than weeks.
- Can I port fsi/gallery-bundle to Laravel instead of rewriting it?
- A port is effectively a rewrite. You could extract the domain model and persistence layer, rebuild container bindings as Laravel service providers, and replace Twig with Blade, but roughly 70% of the package, including container config, views, and Symfony controllers, is discarded. Estimate the same order of magnitude as writing the feature from scratch, plus onboarding onto undocumented decade-old code.
- Does fsi/gallery-bundle work with Laravel's Eloquent or Doctrine?
- Not natively. The bundle assumes Doctrine ORM entities bound through Symfony forms and controllers, while Laravel defaults to Eloquent. You could add Doctrine to Laravel, but that adds complexity for no benefit and still leaves the Symfony integration surfaces unusable.
- How do I implement image uploads, thumbnails, and gallery categories in Laravel?
- Use spatie/laravel-medialibrary to associate uploads with models and generate conversions, intervention/image for thumbnails and variants, and Laravel filesystem disks for storage. Model categories as Eloquent relationships or taxonomy tables. Build gallery views with Blade and route through standard Laravel controllers.
- How would I test a Laravel gallery feature if I reuse ideas from this bundle?
- Test at the Laravel boundaries: Eloquent model factories, Storage::fake for uploads, HTTP tests for gallery endpoints, and assertions on generated image paths. Do not attempt to test Symfony bundle services inside a Laravel test suite. Keep any ported domain logic small and covered by unit tests.
- Who maintains fsi/gallery-bundle and what license does it use?
- FSI Open published it under the MIT license, but there is no active maintainer or community. Forking is legally straightforward with attribution and notice obligations recorded, but you own indefinite self-maintenance. That is a poor trade for a problem already solved by maintained Laravel packages.