Weave Code
Statamic Multisite Forms Laravel Package
uams-web/statamic-multisite-forms
Statamic Multisite Forms extends Statamic's form handling to multisite installations, letting you configure and manage forms per site, route submissions correctly, and keep form data organized across locales and domains.
Per-site forms for multisite Statamic: site assignment, per-site overrides, and site-separated submissions in flat files.
Frequently asked questions about Statamic Multisite Forms
- How do I install uams-web/statamic-multisite-forms in a Laravel project?
- Install it with Composer from Packagist using composer require uams-web/statamic-multisite-forms, then register the add-on and publish its config as described in the package README. As of v0.6.1 the installation instructions document a Packagist source, so you no longer need a VCS repository entry in composer.json. It assumes you already run Laravel with Statamic installed and multisite configured. Pin an explicit version, since the package is still pre-1.0.
- Do I need multisite configured in Statamic to use this package?
- Yes. The add-on extends Statamic's form handling specifically for multisite installations, so it is not applicable to plain Laravel apps or single-site Statamic setups. If you are not already running Statamic multisite with multiple sites, locales, or domains, core Statamic forms are sufficient. The value appears once you need forms scoped per site.
- Are form submissions stored in the database or in flat files?
- Submissions are kept in flat files, separated per site, rather than in your application database. That keeps the add-on aligned with Statamic's file-based storage model and avoids introducing an extra datastore or migration step. The exact file schema and retention policy are not documented in the release notes, so review the package source before committing to a long-term data plan.
- Can I override a form's fields or configuration per site?
- Yes, per-site overrides are one of the core capabilities: you assign a form to a site and override its configuration for that site. This lets the same form definition render differently across locales or domains without duplicating the entire form. The precise override scope, such as fields versus notifications or export behaviour, should be confirmed against the package docs for v0.6.1.
- Which Statamic and PHP versions does this package support?
- The v0.6.1 release notes do not state Statamic or PHP version constraints, so read the composer.json in the repository rather than inferring from documentation. The package is deliberately not listed on the Statamic Marketplace until v1.0.0, and Marketplace review typically enforces version constraints, so expect loose or undocumented constraints today. Verify both axes against your target stack before adopting.
- Is statamic-multisite-forms production ready at v0.6.1?
- Treat it as an early-adopter position rather than a stable production dependency. The maintainers have deferred the Statamic Marketplace listing until v1.0.0, which is an honest signal that the public API, config schema and form data model may still change. There is also no published test coverage signal or failure-mode documentation. Budget for upgrade churn between 0.6.x and 1.0 if you ship it now.
- Does site scoping affect submission routing and notifications, or only form rendering?
- The package description covers site assignment, per-site overrides and site-separated submissions, which implies scoping goes beyond rendering into where submissions land. Whether notification recipients and exports are also site-aware is not spelled out in the release notes. Confirm this in the package code or docs before relying on it for multi-brand notification routing.
- How do I move from a VCS repository install to the Packagist release?
- Remove the custom repositories entry from composer.json and require the package by its Packagist name with an explicit version constraint instead. v0.6.1 is the first release that documents Packagist installation, so it is the natural baseline for the switch. Nothing in that release changes runtime behaviour, so no compatibility re-validation is required beyond the dependency source swap.
- Can existing Statamic form templates adopt this add-on incrementally?
- That depends on whether the add-on hooks Statamic's form tags, its submission pipeline, or both, and the release notes do not specify. If it extends the form tags, existing templates can opt in per form; if it replaces the submission pipeline, migration is more invasive. Read the source or open an issue with the maintainers before planning a partial rollout across templates.
- Is the package actively maintained, and when will v1.0.0 ship?
- UAMS is now the named copyright holder per the v0.6.1 metadata changes, which suggests organisational stewardship rather than a one-off publish. No public 1.0 timeline has been stated beyond the intent to list on the Statamic Marketplace at v1.0.0. v0.6.1 itself is a documentation-only release, so it neither adds nor removes technical capability. If long-term support matters, ask the maintainers directly about their roadmap before committing.
Weaver
How can I help you explore Laravel packages today?