- Can I use endroid/form-bundle in a Laravel application?
- No. Although it is installable via Composer from Packagist, endroid/form-bundle is a Symfony bundle and registers itself through AppKernel::registerBundles(), a Symfony 2/3-era pattern. It ships no Laravel service provider, facade, config publishing or Artisan commands, so there is nothing for Laravel to boot. Composer may resolve the download, but the package will not function inside a Laravel app.
- Is endroid/form-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle. It depends on the Symfony service container and bundle configuration semantics, and it has a hard but undeclared runtime dependency on Sonata Admin Bundle for the actual form-authoring UI. Laravel has no concept of bundles or kernel registration, so the two architectures do not line up.
- How do I install and register endroid/form-bundle?
- In a Symfony application you run composer require endroid/form-bundle and then add new EndroidFormBundle\EndroidFormBundle() to the registerBundles() array in app/AppKernel.php. Forms are then authored through Sonata Admin and rendered in Twig with a controller call such as render(controller('EndroidFormBundle:Form:show', { form: form })). None of these steps map to Laravel.
- What does Endroid FormBundle actually do?
- It lets users create basic forms through Sonata Admin, store the results, send notification or confirmation emails when a form is completed, and export submitted results. When a form is filled in correctly a result is generated and a FormSuccessEvent is dispatched, which built-in listeners use for storage and mailing. Behavior can be extended or overridden by registering your own event listeners.
- Is endroid/form-bundle maintained and safe for production?
- No. The repository is archived, meaning no upstream fixes, no security patches and no compatibility updates, so any defect becomes yours permanently. It has zero stars, zero dependents and no evidence of a production adopter, which makes it effectively unexercised code. For new adoption the archived status alone is disqualifying.
- Does endroid/form-bundle work with current PHP and Laravel versions?
- Unlikely. AppKernel registration and the Sonata Admin coupling imply an old PHP and Symfony floor. Modern Laravel also pulls symfony/* components at pinned versions, so Composer resolution conflicts are plausible even in a quick spike. There is no compatibility path because the repository is archived.
- How do I send a notification email when a form is submitted in Laravel?
- Use Laravel's native notification and mail system rather than a bundle event listener. Dispatch a Notification or Mailable from your form submission controller or a dedicated listener after validation succeeds and the submission record is persisted. This keeps delivery, queuing and templating inside the framework's supported surface and testable with Notification::fake().
- What are the best Laravel alternatives to Endroid FormBundle for dynamic forms?
- For admin-authored dynamic forms, evaluate maintained options such as Filament or Nova form builders, Livewire-based form builders, or a hosted form product. If the requirement is really a handful of known forms plus storage and notification, implementing it natively in Laravel with validation rules, Eloquent models, Notifications and a spreadsheet exporter is only days of work. That route keeps the code owned, testable and upgrade-safe.
- Should I write an adapter to run this Symfony bundle inside Laravel?
- No. A shim would mean booting a mini Symfony container and replicating Sonata Admin's routing and authorization model, then maintaining that bridge indefinitely. That is strictly more work than reimplementing the feature. Port the concept, not the code: a forms table for configuration, a form_submissions table for results, dynamic validation assembled from stored field definitions, a notification on submit and an export via a maintained spreadsheet library.
- What security concerns come with storing and exporting form submissions?
- Form submissions are personally identifiable data, and this bundle ingests, persists, emails and exports them, so an unmaintained component on that path is a data-protection and audit problem. Code of this vintage warrants review for CSRF handling, mass assignment, output escaping in exports and access control on the admin listing of submissions. With no upstream security patches available, any finding stays yours to fix forever.