MegaForm.Umbraco
2.0.44
See the version list below for details.
dotnet add package MegaForm.Umbraco --version 2.0.44
NuGet\Install-Package MegaForm.Umbraco -Version 2.0.44
<PackageReference Include="MegaForm.Umbraco" Version="2.0.44" />
<PackageVersion Include="MegaForm.Umbraco" Version="2.0.44" />
<PackageReference Include="MegaForm.Umbraco" />
paket add MegaForm.Umbraco --version 2.0.44
#r "nuget: MegaForm.Umbraco, 2.0.44"
#:package MegaForm.Umbraco@2.0.44
#addin nuget:?package=MegaForm.Umbraco&version=2.0.44
#tool nuget:?package=MegaForm.Umbraco&version=2.0.44
MegaForm for Umbraco
MegaForm is a schema-driven form and application builder for Umbraco 17 LTS, distributed as a Purchase package. It provides a native backoffice workspace for designing forms, managing submissions, configuring workflows, and publishing forms across Umbraco websites.
Features
- Drag-and-drop form designer in the Umbraco backoffice
- Native Bellissima property editor (
MegaForm.FormPicker) for picking a form on content nodes - Content app showing linked-form summary and recent submissions directly on document workspaces
- Multi-view rendering: inline, modal, embed, script
- Submissions, validation, conditional logic, and rules
- Configurable workflows for processing submissions and integrating external services
- AI-assisted form building and knowledge-base answers
- Static web assets served under
/App_Plugins/MegaForm/
Requirements
- Umbraco 17 LTS (
Umbraco.Cms.Web.Common17.6.1 or later) - .NET 10 or later
Quick start
Install the NuGet package in your Umbraco website project:
dotnet add package MegaForm.UmbracoThe package registers itself automatically via
MegaFormComposer.Use the MegaForm property editor on a Document Type, or render a form in a view:
<megaform form-id="1234" view-type="inline"></megaform>or
@await Component.InvokeAsync("RenderMegaForm", new { formId = 1234, viewType = "inline" })Open the MegaForm section in the Umbraco backoffice to design forms, configure workflows, and review submissions.
Licensing
MegaForm for Umbraco is distributed as a Purchase package. Installing the NuGet package does not grant production usage rights. A valid purchased MegaForm license is required for each production deployment.
To activate an installation, open MegaForm > Settings > License in the Umbraco backoffice and upload the purchased license.lic file. MegaForm validates the file using its current license mechanism and stores it privately at App_Data/MegaForm/license.lic. Umbraco activation does not use the Oqtane Marketplace license flow.
While MegaForm is in trial mode, the backoffice banner exposes two separate actions:
- Purchase opens the configured checkout/download destination in a new tab.
- Activate license opens the MegaForm > Settings > License pane directly, where an administrator can upload
license.lic.
Uploading a valid license updates the status in place to Active; it does not redirect the administrator to an external site.
For direct sales, keep the NuGet package and license as separate files. The customer
installs the unchanged production .nupkg from the configured NuGet source, then uploads
their personalized license.lic through MegaForm > Settings > License. MegaForm accepts
the legacy one-line production marker and the lightweight email-bound form below:
production
email-sha256:<64 lowercase hexadecimal characters>
The hash is SHA-256 of the customer's trimmed, lowercase email address. The production package itself contains no customer-specific license.
Contact the MegaForm team through the project links below for licensing, pricing, evaluation access, and support.
Purchase link configuration
On first use, MegaForm creates App_Data/MegaForm/megaform-settings.json. Edit this site-owned file to choose a package type and the destination opened by the Purchase action. Activate license remains a separate action and opens the built-in license.lic upload screen:
{
"activePackageType": "Purchase",
"packages": {
"Purchase": {
"purchaseUrl": "https://example.com/megaform/purchase"
},
"Professional": {
"purchaseUrl": "https://example.com/megaform/professional"
}
}
}
Package keys are case-insensitive. Purchase URLs may be absolute http/https URLs or site-relative paths beginning with /. The file is read on each request, so changing it does not require rebuilding or reinstalling MegaForm. Package upgrades do not overwrite it.
Marketplace
This package is listed on the official Umbraco Marketplace as a Purchase package and is tagged umbraco-marketplace for compatibility discovery.
Documentation and support
- Documentation: https://github.com/CissSolution/MegaformDocs
- Issues: https://github.com/CissSolution/MegaformDocs/issues
- Discussions: https://github.com/CissSolution/MegaformDocs/discussions
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- AWSSDK.S3 (>= 4.0.101.4)
- Microsoft.EntityFrameworkCore (>= 10.0.8)
- Microsoft.EntityFrameworkCore.Sqlite (>= 10.0.8)
- Microsoft.EntityFrameworkCore.SqlServer (>= 10.0.8)
- Newtonsoft.Json (>= 13.0.3)
- SQLitePCLRaw.lib.e_sqlite3 (>= 2.1.12)
- Umbraco.Cms.Core (>= 17.6.1 && < 18.0.0)
- Umbraco.Cms.Infrastructure (>= 17.6.1 && < 18.0.0)
- Umbraco.Cms.Web.Common (>= 17.6.1 && < 18.0.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
MegaForm 2.0.44 for Umbraco 17 LTS. Makes the native Form Settings view follow the Umbraco backoffice language before any stale shared locale, and cache-busts that native view to prevent a previously loaded translation bundle from producing mixed English/Vietnamese labels. Adds the simple customer-email SHA-256 license.lic format used by direct-sale downloads while preserving legacy production licenses. Retains JSON-configured Purchase and direct Activate license actions, workflow retry history, submission detail fixes, selective Copy workflows, and the one-package bundled runtime.