Version Specific Upgrade Notes
Version specific documentation for upgrading to new major versions of Umbraco Forms.
Last updated
Was this helpful?
Version specific documentation for upgrading to new major versions of Umbraco Forms.
This article provides specific upgrade documentation for migrating to Umbraco Forms version 17.
If you are upgrading to a minor or patch version, you can find the details about the changes in the Release Notes article.
Version 17 of Umbraco Forms has a minimum dependency on Umbraco CMS core of 17.0.0. It runs on .NET 10.
This change was introduced in version 14. It affects you if you upgrade directly from version 13 to version 17.
In version 13, Forms tracked the forms rendered on a page using TempData. From version 14 onwards, the default value of the TrackRenderedFormsStorageMethod configuration option is HttpContextItems.
If your template renders form scripts using a custom snippet that reads the rendered form IDs from TempData, the snippet no longer finds them. As a result, the form scripts and any assets registered by custom field types stop rendering.
The scripts fail silently. Forms still submit, but conditional logic, field behaviors, and custom field type assets are missing from the page.
To resolve this, choose one of the following options:
Update your snippet to read the rendered form IDs from HttpContext.Items.
Use the <umb-forms-render-scripts /> tag helper, which respects the configured storage method.
Set TrackRenderedFormsStorageMethod back to TempData to keep the version 13 behavior.
For the updated snippets and the tag helper, see the Rendering Forms Scripts article. For the configuration option, see the Configuration article.
You can find the version specific upgrade notes for versions out of support in the Legacy documentation on GitHub.
Last updated
Was this helpful?
Was this helpful?