Weave Code
Contact Bundle Laravel Package
sylius/contact-bundle
Sylius Contact Bundle adds a configurable contact form to your Sylius storefront and lets administrators review and manage submitted contact requests from the admin panel, integrating with Sylius resources, channels, and email notifications.
[READ-ONLY] Sylius contact form and support system bundle.
Frequently asked questions about Contact Bundle
- Can I use sylius/contact-bundle in a Laravel application?
- No. It is a Symfony/Sylius bundle built on Symfony forms, routing, security, Doctrine resources, and Sylius resource configuration, so it will not integrate with Laravel's container, Eloquent, Blade, or middleware. Treat it as a reference for contact intake workflow rather than a Composer dependency for Laravel.
- What does sylius/contact-bundle do?
- It adds a configurable contact form to a Sylius storefront and lets administrators review and manage submitted contact requests. It integrates with Sylius resources, channels, and email notifications. It is part of the Sylius e-commerce stack, not a general Laravel package.
- Is sylius/contact-bundle maintained?
- No, the repository is archived and read-only. It will not receive security patches, bug fixes, or compatibility updates. Any use means you own forking, patching, dependency upgrades, and testing.
- Which Laravel versions does sylius/contact-bundle support?
- None. The package targets Sylius and Symfony versions and has no Laravel service provider, facade, config publishing, migrations, or Blade views. Laravel compatibility is not part of its support matrix.
- How do I install sylius/contact-bundle?
- In a Sylius application you would install it with Composer and register or configure it following Sylius bundle conventions, including resource and routing configuration. There is no Laravel installation path. Because the package is archived, verify PHP, Symfony, Doctrine, and Sylius version constraints before attempting installation.
- What are alternatives to sylius/contact-bundle for Laravel?
- Build a small Laravel-native module using form requests for validation, an Eloquent model for contact messages, queued mailables or notifications for email, middleware and policies for admin access, rate limiting for abuse control, and a Filament or Nova resource for triage. This avoids Symfony/Sylius coupling and gives you maintained dependencies. If you need a support workflow, add statuses, assignment, audit history, and CRM/helpdesk hooks.
- Can I integrate sylius/contact-bundle with Laravel's admin panel?
- No direct integration is realistic. The bundle's admin screens rely on Sylius grid and resource conventions, not Laravel admin tools. Reimplementing the workflow in Filament, Nova, or custom Blade views is faster and safer than bridging the two stacks.
- What should I check before using sylius/contact-bundle in production?
- Confirm you are running Sylius and that your current Sylius version does not already include contact-request functionality, which could create duplicate routes or services. Define spam controls, rate limiting, email deliverability monitoring, admin triage, and PII retention and consent rules. Because the bundle is archived, assign ownership for security patching, dependency pinning, tests, and upgrade planning.
- Does sylius/contact-bundle work with Symfony forms and Doctrine?
- Yes, it is designed around Symfony forms, Doctrine resources, and Sylius resource configuration. That is exactly why it does not fit Laravel, which uses different form validation, ORM, and admin conventions. The bundle's architecture is Symfony/Sylius-specific.
- How should I test sylius/contact-bundle?
- In a Sylius context, test the public submission flow, validation failures, persistence, channel scoping, email notification dispatch, and admin review actions. For Laravel, do not test the bundle; instead test your native implementation with feature tests for form validation, rate limiting, queued mail, authorization, and PII handling. Since the bundle is archived, any fork needs its own regression and compatibility test suite.
Weaver
How can I help you explore Laravel packages today?