Weave Code
Simplecontactform Widget Laravel Package
friendsofvictoire/simplecontactform-widget
A lightweight widget for adding a simple contact form to Laravel/PHP applications. It provides reusable form UI and basic submission handling, keeping contact form integration quick and easy.
Simple Contact Form Widget is a lightweight Laravel package that adds a ready-made contact form to your application with minimal setup. It handles rendering, validation, and submission so you can start collecting inquiries without building a form from scratch.
- Drop-in Blade component for instant embedding
- Built-in validation for name, email, and message fields
- Configurable recipients and success messages
- Publishable views for full styling control
- Simple hooks for custom spam protection
Frequently asked questions about Simplecontactform Widget
- Can I use friendsofvictoire/simplecontactform-widget in a Laravel application?
- No. It is a Symfony bundle for Victoire DCMS, not a Laravel package; it has no Laravel service providers, Blade views, or Illuminate dependencies. Dropping it into Laravel is unsupported and would require reimplementation. For Laravel, build a native contact form with a route, FormRequest, Mailable, and Blade partial.
- What is friendsofvictoire/simplecontactform-widget used for?
- It was a contact-form widget for Victoire DCMS, a Symfony page-builder CMS. It registered a name, email, and message form with validation and mail sending into Victoire's editor. It is marked deprecated and is not intended for new projects.
- Is this package still maintained?
- No. The last release was 2017-03-14, with 1 star and 0 dependents, and there has been no maintenance signal for roughly eight years. It is marked DEPRECATED and has no upstream CVE response. Assume full ownership if adopted.
- Does it support Laravel 10 or Laravel 11?
- No. The package is a Symfony and Victoire bundle from the Symfony 2.8/3.x and PHP 5.6/7.0 era, so it has no Laravel version support. Composer resolution will likely fail on PHP 8.x and modern Laravel without patching. Use native Laravel components instead.
- How do I install friendsofvictoire/simplecontactform-widget?
- You would normally require it in a Victoire and Symfony project via Composer, but the legacy constraints may not resolve on modern PHP or Symfony. There is no supported Laravel install path and no Laravel-style config publishing. For Laravel, do not install it; implement the form natively.
- What are the alternatives for a Laravel contact form?
- Implement a route, FormRequest validation, Mailable, and Blade partial using Laravel's built-in CSRF protection and queued mail. Add a honeypot or rate limiter for spam. This removes the abandoned dependency and typically takes one to two days including tests.
- Does this bundle include CSRF protection and spam prevention?
- The functional surface is small: a name, email, and message form, validation, and a mail send. The assessment flags unmaintained CSRF, spam, and mail-transport handling as compliance and abuse exposure, so you must verify or add these controls. Do not assume production-grade protection.
- Can I use it with Symfony 5 or Symfony 6?
- Probably not without patching. The bundle targets the 2017-era Symfony 2.8/3.x and PHP 5.6/7.0 baseline, and its Composer constraints are expected to be in the ~2.8|~3.0 range. Check composer.json first and plan for a constrained legacy environment or a fork.
- How should I test a contact form in Laravel?
- Use Laravel feature tests to assert validation errors, successful submission, CSRF behavior, and that a Mailable is sent or queued. Mock or fake the mail transport and cover spam controls such as a honeypot or rate limiting. Keep tests around the native implementation rather than the abandoned bundle.
- What are the production risks of adopting this widget?
- It is abandoned, end-of-life on PHP and Symfony, and has no security patching or community support. The form is user-facing and handles PII, so unmaintained CSRF, spam, and mail handling are compliance and abuse risks. Name an internal owner and decide explicitly to adopt, fork, or replace before merge.
Weaver
How can I help you explore Laravel packages today?