Weave Code
Contact Bundle Laravel Package
frequence-web/contact-bundle
Contact bundle from Frequence Web for PHP applications. Adds reusable contact form handling so you can capture, store, and manage incoming contact requests through a simple configurable integration. Ideal for adding a ready-made contact workflow to Symfony/PHP projects without building form and pers...
A simple contact bundle
Frequently asked questions about Contact Bundle
- Is frequence-web/composer contact-bundle compatible with Laravel?
- No. The package name and namespace indicate a Symfony bundle that relies on Symfony DependencyInjection, HttpKernel, and EventDispatcher conventions, not Laravel service providers, config publishing, or Illuminate events. Treat it as a design reference rather than a Laravel dependency.
- Can I install frequence-web/contact-bundle with Composer in a Laravel project?
- Composer installation is likely to fail or force incompatible downgrades. The bundle has Symfony 2-era constraints and no illuminate/* dependencies, so it can collide with the Symfony contracts already used by modern Laravel. Vendor the source only if you need to read or audit it.
- What does FrequenceWebContactBundle actually do?
- It provides reusable contact form handling for Symfony/PHP applications, including capturing and storing incoming contact requests. Its main reusable idea for Laravel teams is the contact lifecycle pattern, where events are dispatched for submission, validation, persistence, and notification. The implementation itself is Symfony-specific.
- How do I add a contact form workflow to Laravel using this bundle's ideas?
- Do not port the Symfony container wiring or YAML service definitions. Instead, extract the event contracts and dispatch points, then reimplement them with Laravel service providers, config/contact.php, and Illuminate event listeners. Build this as an internal package such as acme/laravel-contact-events with feature tests.
- Which PHP and Laravel versions does frequence-web/contact-bundle support?
- No Laravel versions are confirmed. There is no Laravel service provider, no Illuminate dependency, and no evidence of Laravel version constraints. The package appears to target Symfony 2-era PHP and Symfony component versions, which conflict with modern Laravel requirements.
- What are the alternatives for contact form handling in Laravel?
- For a native Laravel solution, use Laravel's form validation, Eloquent models, notifications, and events to build a small contact workflow. If you want a package, choose one with explicit illuminate/support constraints and a Laravel service provider. This bundle is not a drop-in alternative for Laravel.
- Is frequence-web/contact-bundle maintained and safe for production?
- The assessment shows no active maintainer signal, no release cadence, and no security response capability. It has no test or adoption evidence in the provided context, and contact flows handle PII, validation, and notification paths where silent failures matter. Production use in Laravel is high risk.
- How do I migrate the bundle's Symfony events to Laravel events?
- Map Symfony EventDispatcher dispatch sites to Illuminate\Contracts\Events\Dispatcher and replace bundle listeners with Laravel listeners or Event::listen registrations. Convert extension configuration into a publishable config/contact.php using mergeConfigFrom and publishes. Reimplement bundle bootstrapping as a package service provider.
- Can I fork frequence-web/contact-bundle and port it to Laravel?
- Yes, the MIT license is permissive, so forking and porting concepts carries no legal friction beyond attribution obligations. Keep the MIT notice for any ported logic, but reimplement Symfony wiring instead of transliterating it. Assign an owner for maintenance and a security review path for PII-handling code.
- How should I test a Laravel port of this contact workflow?
- Write feature tests around form submission, validation failures, persistence, event dispatch, and notification listeners. Use Laravel's event fakes and notification fakes to assert lifecycle behavior without external services. Also test configuration publishing and service provider bindings so the ported package behaves predictably.
Weaver
How can I help you explore Laravel packages today?