From cd63fc2b3a4fc842a23affd3fa69db020f6041ba Mon Sep 17 00:00:00 2001 From: Jonathon Cove Date: Wed, 20 Aug 2025 11:28:06 +0100 Subject: [PATCH 1/2] Update rendering-forms.md Mention that the includeScripts is necessary for conditional fields to render --- 13/umbraco-forms/developer/rendering-forms.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/13/umbraco-forms/developer/rendering-forms.md b/13/umbraco-forms/developer/rendering-forms.md index 77f17bb3060..c3ed4891081 100644 --- a/13/umbraco-forms/developer/rendering-forms.md +++ b/13/umbraco-forms/developer/rendering-forms.md @@ -18,7 +18,7 @@ Six parameters can be provided: - `formId` is the GUID of a form. - `theme` is the name of a theme. If not provided, the default theme is used (see [Themes](./themes.md)). -- `includeScripts` indicates whether scripts should be rendered with the form (see [Rendering Scripts](./rendering-scripts.md). +- `includeScripts` indicates whether scripts should be rendered with the form (necessary to use conditional fields, see [Rendering Scripts](./rendering-scripts.md)). - `recordId` is an optional existing record GUID, used if editing records via the website is [enabled in configuration](../developer/configuration/README.md#alloweditableformsubmissions) - `redirectToPageId` is an optional GUID for a content page that, if provided, is redirected to once the form has been submitted. It will be used in preference to post-submission behavior defined on the form itself. - `additionalData` is an optional dictionary of string values. When provided it will be used as a source for ["magic string" replacements](./magic-strings.md). The data will be associated with the created record and made available for custom logic or update within workflows. @@ -71,4 +71,4 @@ Similarly, you can reference a form picker property on your page: { @await Umbraco.RenderMacroAsync("renderUmbracoForm", new { FormGuid = formId, FormTheme = Model.FormTheme, ExcludeScripts = "1" }) } -``` \ No newline at end of file +``` From 83addc869f059b12804b88c35ef5f0388aeac58d Mon Sep 17 00:00:00 2001 From: sofietoft Date: Wed, 10 Sep 2025 09:24:03 +0200 Subject: [PATCH 2/2] Update 13/umbraco-forms/developer/rendering-forms.md --- 13/umbraco-forms/developer/rendering-forms.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/13/umbraco-forms/developer/rendering-forms.md b/13/umbraco-forms/developer/rendering-forms.md index c3ed4891081..47f8f023574 100644 --- a/13/umbraco-forms/developer/rendering-forms.md +++ b/13/umbraco-forms/developer/rendering-forms.md @@ -18,7 +18,7 @@ Six parameters can be provided: - `formId` is the GUID of a form. - `theme` is the name of a theme. If not provided, the default theme is used (see [Themes](./themes.md)). -- `includeScripts` indicates whether scripts should be rendered with the form (necessary to use conditional fields, see [Rendering Scripts](./rendering-scripts.md)). +- `includeScripts` indicates whether scripts should be rendered with the form. This is necessary for using conditional fields. See [Rendering Scripts](./rendering-scripts.md) for more details. - `recordId` is an optional existing record GUID, used if editing records via the website is [enabled in configuration](../developer/configuration/README.md#alloweditableformsubmissions) - `redirectToPageId` is an optional GUID for a content page that, if provided, is redirected to once the form has been submitted. It will be used in preference to post-submission behavior defined on the form itself. - `additionalData` is an optional dictionary of string values. When provided it will be used as a source for ["magic string" replacements](./magic-strings.md). The data will be associated with the created record and made available for custom logic or update within workflows.