Weave Code
Form Widget Laravel Package
friendsofvictoire/form-widget
Form widget for Victoire: adds a reusable component for embedding and managing forms inside the Victoire CMS page builder, so editors can place and configure form content directly in their layouts without custom integration work.
Create custom forms in Victoire website
Frequently asked questions about Form Widget
- Is friendsofvictoire/form-widget a Laravel package?
- No. friendsofvictoire/form-widget is a Symfony bundle built for the Victoire CMS, not a Laravel package. It ships no Laravel service provider, facade, or publishable config stub. Installing it in a Laravel app would drag in Symfony Form, HttpKernel, DependencyInjection, and EventDispatcher plus Victoire's widget registry. If your intake ticket said Laravel, correct the scope before estimating.
- How do I install friendsofvictoire/form-widget?
- Install it with Composer inside a Symfony application that already runs Victoire, so Symfony bundle auto-registration and Victoire's widget registry are available. There is no Laravel install path and no config:publish step. Check the bundle's composer.json for its PHP and Symfony constraints before you try anything.
- Which Laravel versions does this package support?
- None. The package targets Symfony and Victoire, so there is no Laravel version support matrix at all. There is also no supported bridge from Symfony Form to Laravel's validator or form builder. Plan on rebuilding the form behaviour natively in Laravel.
- What does the Form widget actually do in Victoire?
- It registers a Form widget in Victoire's page editor so an editor can drop a form onto a page and define fields through the widget configuration UI. Rendering is handled by Symfony Form. All of the value depends on already running Victoire as your CMS.
- Can I use this form widget in an existing Laravel application?
- Not without unsupported glue code. You would need Symfony Form, HttpKernel, DependencyInjection, and EventDispatcher plus Victoire's Widget base classes, asset pipeline, and templating. The historical Symfony Form integrations for Laravel are unmaintained, so you would own that glue with no upstream.
- Where are form submissions stored, and is it suitable for GDPR?
- Submissions are persisted through Doctrine in the Victoire database schema, so personal data lands in a store you do not control and cannot easily audit. Retention, export, and deletion policies are yours to define. Assess that before putting any PII through it.
- Does it include CSRF protection, captcha, honeypot, or rate limiting?
- CSRF and validation behaviour come from Symfony Form configuration rather than Laravel middleware. Honeypot, captcha, and rate-limiting hooks are not clearly provided, so you would own spam mitigation end-to-end. Verify on the exact branch you would deploy.
- What Symfony and PHP versions does it require?
- The bundle's composer.json is the source of truth, and it will be pinned to whatever Symfony versions Victoire supported. Victoire itself has been effectively dormant for years, so upstream security patching is unlikely. Confirm your PHP and Symfony versions still receive security support.
- Is friendsofvictoire/form-widget actively maintained and production-ready?
- There is no production signal: zero stars, zero dependents, and zero downstream consumers. That means no real-world usage to surface bugs and no third party who would notice a regression. Treat it as an internal fork candidate at best, not a dependency.
- What are the alternatives, and is there a migration path to Laravel?
- For Laravel, use an actively maintained form-builder package with a Filament or Nova admin surface, or embed a hosted form product via iframe. For a legacy Victoire site, evaluate the bundle in place with a hard sunset date. There is no incremental migration from this widget into Laravel.
Weaver
How can I help you explore Laravel packages today?