- What is rapidez/statamic-quote used for?
- rapidez/statamic-quote adds quote-request functionality to Rapidez storefronts that use Statamic. Customers can submit product enquiries and receive tailored pricing, while quote content and settings are managed in Statamic. The package is installed as a Composer dependency in a Laravel application.
- How do I install rapidez/statamic-quote in a Laravel project?
- Install it with Composer using the package name rapidez/statamic-quote, then follow the repository README for Rapidez and Statamic configuration. The overview describes Laravel and PHP support for easy installation, but the exact service provider, config, and publish steps are not included in the provided release notes. Confirm the current setup instructions in the README before scheduling work.
- Does rapidez/statamic-quote support file uploads?
- Yes, release 2.2.0 adds file upload support to file fields. This moves the package beyond metadata and form definitions into request handling and storage. Existing file fields are likely to keep working if no upload configuration is supplied, but you should verify that behavior in a non-production branch.
- Which Laravel and PHP versions does rapidez/statamic-quote support?
- The provided release notes do not state a Laravel or PHP version support matrix. Because file handling often depends on framework-version-specific APIs, check the package composer.json and README before upgrading. Confirm compatibility with your Rapidez and Statamic versions as well.
- How does file upload validation work in rapidez/statamic-quote 2.2.0?
- The release notes only summarize file upload support for file fields, so server-side validation behavior is not confirmed. Before using it with user-facing forms, verify that size and MIME-type limits are enforced independently of client-controlled form definitions. If validation exists only at the form-definition layer, add framework-level validation rules for production use.
- Where are uploaded files stored with rapidez/statamic-quote?
- The technical assessment places the upload feature between the HTTP layer and Laravel's filesystem abstraction, so storage should depend on your configured disks and visibility settings. The release notes do not confirm whether S3 or other non-local storage is first-class, or how filenames are generated. Review the README and test your target disk before enabling uploads in production.
- Are uploaded files deleted when a quote record is deleted?
- There is no evidence in the provided release notes of cascade cleanup when a record is deleted, a field is removed, or a submission is abandoned. Orphaned files are a realistic risk with file upload features, especially on public disks. Confirm cleanup behavior and plan a retention or pruning strategy before production use.
- Is rapidez/statamic-quote safe for production file uploads?
- Treat the 2.2.0 file upload feature as an opt-in capability and assess it carefully for user-facing forms. The main risks are storage lifecycle, MIME and extension trust, path traversal in generated filenames, public-disk exposure, and compliance obligations for sensitive documents. For prototypes or internal tools the integration cost is low; for production, scope validation, disk visibility, cleanup, and retention first.
- How does rapidez/statamic-quote integrate with Statamic?
- It lets Statamic manage quote content and settings while Rapidez provides the storefront quote-request flow. The package sits in a Laravel application and integrates with Composer-based installation. The provided overview does not detail the exact Statamic blueprints, fields, or control-panel configuration, so check the README for the current setup.
- When should I avoid the file upload feature in rapidez/statamic-quote?
- Avoid it if your application already centralizes uploads in a dedicated media library, DAM, or virus-scanning pipeline, because the package would introduce a second upload path. Also avoid it for sensitive documents until you confirm server-side validation, private disk support, filename safety, and cleanup behavior. For those cases, keep uploads in your existing service and use the package only for quote-request metadata.