Merge branch 'main' into v17/update-repository-docs

Author: madsrasmussen

13/umbraco-engage/getting-started/for-developers/troubleshooting-installations.md

@@ -16,7 +16,7 @@ The most common reasons for this are:
 
 * Database connectivity issues.
 * Incompatible SQL Server version.
-* No COLUMNS STORE index support on Azure SQL lower than S3.
+* No columnstore index support on Azure SQL lower than S3.
 
 ### Exception
 
@@ -41,7 +41,7 @@ await app.BootUmbracoAsync();
 
 #### When having database connectivity issues
 
-1. Remove the row with the `Umbraco.Core.Upgrader.State+Umbraco.Engage` key from the `umbracoKeyValue` table in the database if it exists. 
+1. Remove the row with the `Umbraco.Core.Upgrader.State+Umbraco.Engage` key from the `umbracoKeyValue` table in the database if it exists.
 2. Remove all existing umbracoEngage\* tables from the database if they exist.
 3. Restart the site.
 
@@ -51,10 +51,10 @@ await app.BootUmbracoAsync();
 When running Azure SQL on lower tiers and querying columnstore indexes, performance may decrease. Depending on the amount of data being processed, this can also lead to timeouts. This configuration is not recommended for production environments.
 {% endhint %}
 
-Azure SQL lower than S3 doesn't support creating COLUMN STORE indexes. To work around this follow these steps: 
+Azure SQL lower than S3 doesn't support creating columnstore indexes. To work around this follow these steps:
 
 1. Scale your Azure SQL environment to S3.
 2. Restart the site.
 3. Scale back to your initial Azure SQL tier.
 
-The columnstore indexes are created and can be used in a lower tier. 
+The columnstore indexes are created and can be used in a lower tier.

13/umbraco-forms/developer/files/umbraco-forms-default-theme-13.7.0-rc.zip renamed to 13/umbraco-forms/developer/files/umbraco-forms-default-theme-13.7.0.zip

@@ -26,7 +26,7 @@ You can obtain the latest version of the Forms default theme from the following
 * [13.2.4](./files/umbraco-forms-default-theme-13.2.4.zip)
 * [13.3.0](./files/umbraco-forms-default-theme-13.3.0.zip)
 * [13.5.0](./files/umbraco-forms-default-theme-13.5.0.zip)
-* [13.7.0-rc](./files/umbraco-forms-default-theme-13.7.0-rc.zip)
+* [13.7.0](./files/umbraco-forms-default-theme-13.7.0.zip)
 
 You should use the theme available for the highest version that's less or equal to the version of Forms you have installed. For example, when using Umbraco Forms 13.4.0, and no file for that version is available use version 13.3.0 instead.
 

13/umbraco-forms/developer/themes.md

@@ -16,6 +16,9 @@ If you are upgrading to a new major version, you can find information about the
 
 This section contains the release notes for Umbraco Forms 13 including all changes for this version.
 
+### [13.7.0](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue%20state%3Aopen%20label%3Arelease%2F13.7.0) (October 30th 2025)
+* All items detailed under release candidates for 13.7.0.
+
 ### [13.7.0-rc2](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue%20state%3Aopen%20label%3Arelease%2F13.7.0) (October 27th 2025)
 * Improved redirects in UmbracoFormsController for handling IContentFinder and virtual pages [#1456](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1456)
 * Fix prevalue source to sort by caption by default, not value [#1438](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1438)

13/umbraco-forms/release-notes.md

@@ -17,6 +17,11 @@ Check the [Version Specific Upgrade Notes](upgrading/version-specific.md) articl
 
 This section contains the release notes for Umbraco Workflow 13 including all changes for this version.
 
+### 13.4.6 (October 31 2025)
+* Fixes a bug where rejected tasks were shown as pending approval for users belonging to the rejecting group.
+* Fixes a bug where Advanced Search could not find property editor views.
+* Updates Umbraco.Licenses dependency to 13.3.3.
+
 ### [13.4.5](https://github.com/umbraco/Umbraco.Workflow.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F13.4.5) (July 30 2025)
 * Ensures inherited group members are always populated [#111](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/111)
 * Adds an option to disable the remote version check [#99](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/99)

13/umbraco-workflow/release-notes.md

@@ -20,6 +20,7 @@ A full configuration with all default values can be seen here:
       "UsernameIsEmail": true,
       "MemberRequireUniqueEmail": true,
       "AllowedUserNameCharacters": "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789-._@+\\",
+      "BackOfficeHost": "http://your-domain.com",
       "UserPassword": {
         "RequiredLength": 10,
         "RequireNonLetterOrDigit": false,
@@ -84,6 +85,10 @@ By default Umbraco will not allow creation of more than one member account with
 
 Defines the allowed characters for a username.
 
+### BackOffice Host
+
+Use this setting to override the Backoffice host URL. This is useful when the Backoffice client runs from a different origin than the Umbraco server. For example, in proxied, cloud-hosted setups, or when developing locally using Vite or another dev server.
+
 ### User default lockout time
 
 Use this setting to configure how long time a User is locked out of the Umbraco backoffice when a lockout occurs. The setting accepts an integer which defines the lockout in minutes.

15/umbraco-cms/reference/configuration/securitysettings.md

@@ -1,5 +1,5 @@
 ---
-description: Example on how to create and publish content programmatically using the ContentService.
+description: Example on how to create and publish content programmatically using the `IContentService`.
 ---
 
 # Content Service
@@ -8,7 +8,9 @@ Learn how to use the Content Service.
 
 ## Creating content programmatically
 
-In the example below, a new page is programmatically created using the content service. It is assumed that there are two document types, namely Catalogue and Product. In this case, a new Product is added underneath the Catalogue page. Add the below code in the Catalogue template.
+In the example below, a new content item is programmatically created using the content service. It is assumed that there are two document types, namely *Catalogue* and *Product*. A new *Product* node will be created under the *Catalogue* page.
+
+Create a new C# class file (for example, `MyProject/Services/PublishContentDemo.cs`) inside your web project.
 
 ```csharp
 using Umbraco.Cms.Core.Models;
@@ -36,9 +38,12 @@ public class PublishContentDemo
         // Set the value of the property with alias 'price'
         demoProduct.SetValue("price", "1500");
 
-        // Save and publish the child item
+        // Save content first
         _contentService.Save(demoProduct);
-        _contentService.Publish(demoProduct, ["en-us", "da"]);
+
+        // Publish content
+        var userId = 0; // 0 = system user
+        _contentService.Publish(demoProduct, new[] { "*" }, userId); // use "*" for invariant content
     }
 }
 ```
@@ -54,35 +59,39 @@ For information on how to retrieve multilingual languages, see the [Retrieving l
 
 ## Publishing content programmatically
 
-The ContentService is also used for publishing operations.
+The `IContentService` is also used for publishing existing content. The following example shows how to publish a page and all its descendants.
 
-The following example shows a page being published with all descendants.
+Create a new C# class file (for example, `MyProject/Services/PublishBranchContentDemo.cs`) inside your web project.
 
 ```csharp
 using Umbraco.Cms.Core.Models;
 using Umbraco.Cms.Core.Services;
 
 namespace Umbraco.Cms.Web.UI.Custom;
 
-public class PublishContentDemo
+public class PublishBranchContentDemo
 {
     private readonly IContentService _contentService;
 
-    public PublishContentDemo(IContentService contentService) => _contentService = contentService;
+    public PublishBranchContentDemo(IContentService contentService) => _contentService = contentService;
 
     public void Publish(Guid key)
     {
-        IContent? content = _contentService.GetById(key)
+        var parentKey = Guid.Parse("b6fbbb31-a77f-4f9c-85f7-2dc4835c7f31");
+
+        var content = _contentService.GetById(key)
             ?? throw new InvalidOperationException($"Could not find content with key: {key}.");
 
-        _contentService.PublishBranch(content, PublishBranchFilter.Default, ["en-us", "da"]);
+        var userId = 0;
+        _contentService.PublishBranch(content, PublishBranchFilter.Default, new[] { "*" }, userId);
     }
 }
 ```
 
 The `PublishBranchFilter` option can include one or more of the following flags:
 
-- `Default` - publishes existing published content with pending changes.
-- `IncludeUnpublished` - publishes unpublished content and existing published with pending changes.
-- `ForceRepublish` - publishes existing published content with or without pending changes.
+- `Default` - publishes only nodes with pending changes.
+- `IncludeUnpublished` - publishes unpublished content and existing nodes with pending changes.
+- `ForceRepublish` - republishes all nodes, even if unchanged.
 - `All` - combines `IncludeUnpublished` and `ForceRepublish`.
+- For multilingual content, replace `"*"` with the array of cultures, for example, `new[] { "en-us", "da" }`.

15/umbraco-cms/reference/management/using-services/contentservice.md

@@ -147,3 +147,4 @@ redirects:
     customizing/extending-overview/extension-registry/extension-registry: customizing/extending-overview/extension-registry/register-extensions.md
     customizing/extending-overview/extension-types/workspaces/workspace-action-menu-item: customizing/extending-overview/extension-types/workspaces/workspace-action-menu-items.md
     customizing/extending-overview/extension-types/workspaces/workspace-footer-app: customizing/extending-overview/extension-types/workspaces/workspace-footer-apps.md
+    customizing/extending-overview/extension-kind: customizing/extending-overview/extension-types/kind.md

16/umbraco-cms/.gitbook.yaml

@@ -153,9 +153,9 @@
   * [Vite Package Setup](customizing/development-flow/vite-package-setup.md)
 * [Extensions Overview](customizing/extending-overview/README.md)
   * [Extension Registry](customizing/extending-overview/extension-registry/README.md)
+    * [Extension Manifest Introduction](customizing/extending-overview/extension-registry/extension-manifest.md)
     * [Register an Extension](customizing/extending-overview/extension-registry/register-extensions.md)
-    * [Extension Manifest](customizing/extending-overview/extension-registry/extension-manifest.md)
-    * [Replace, Exclude or Unregister](customizing/extending-overview/extension-registry/replace-exclude-or-unregister.md)
+    * [Replace, Exclude, or Unregister](customizing/extending-overview/extension-registry/replace-exclude-or-unregister.md)
   * [Extension Types](customizing/extending-overview/extension-types/README.md)
     * [App Entry Point](customizing/extending-overview/extension-types/app-entry-point.md)
     * [Backoffice Entry Point](customizing/extending-overview/extension-types/backoffice-entry-point.md)
@@ -188,7 +188,8 @@
       * [Workspace Context](customizing/extending-overview/extension-types/workspaces/workspace-context.md)
       * [Workspace Views](customizing/extending-overview/extension-types/workspaces/workspace-views.md)
       * [Workspace Footer Apps](customizing/extending-overview/extension-types/workspaces/workspace-footer-apps.md)
-  * [Extension Kind](customizing/extending-overview/extension-kind.md)
+    * [Collections](customizing/extending-overview/extension-types/collections/README.md)
+      * [Collection View](customizing/extending-overview/extension-types/collections/collection-view.md)
   * [Extension Conditions](customizing/extending-overview/extension-conditions.md)
   * [Custom Extension types](customizing/extending-overview/custom-extension-type.md)
 * [Foundation](customizing/foundation/README.md)

16/umbraco-cms/SUMMARY.md

@@ -23,6 +23,7 @@ For example, a Document scheduled for future publishing will have a Flag defined
 A Flag can be the determinant for a Sign by declaring the `forEntityFlags` as part of its Manifest.
 
 Example:
+
 ```json
 ...
 forEntityFlags: "Umb.ScheduledForPublish",
@@ -33,7 +34,88 @@ Using this binding lets the server determine which signs are present in the resp
 
 ## Displaying a Sign
 
+To display a Sign in the backoffice, register an `entitySign` extension.
+
+Typically, you’ll bind it to one or more flags returned in the server response using the `forEntityFlags` property. However, you can also provide your own logic to determine when a Sign should appear.
+
+If you're using an icon variant, set `kind` to `icon` and provide both `meta.iconName` and `meta.label`. This ensures the user interface has the necessary visual and accessible information to render the Sign correctly.
+
+### Example: Rendering an Entity Sign from a Server Flag
+
+```typescript
+import type { UmbExtensionManifest } from "@umbraco-cms/backoffice/extension-registry";
+import { UMB_DOCUMENT_ENTITY_TYPE } from "@umbraco-cms/backoffice/document";
+
+export const manifests: UmbExtensionManifest = {
+    type: "entitySign",
+    kind: "icon",
+    alias: "Umb.EntitySign.Document.IsProtected",
+    name: "Is Protected Document Entity Sign",
+    forEntityTypes: [UMB_DOCUMENT_ENTITY_TYPE], // Where it can appear
+    forEntityFlags: ["Umb.IsProtected"], // <---Binding part-When it should appear
+    weight: 1000,
+    meta: {
+        iconName: "icon-lock", // Built-in or custom icon name
+        label: "Protected", // Visible/accessible label
+        iconColorAlias: "red",
+    },
+};
+```
+
+When an entity includes the `Umb.IsProtected` flag, this Sign appears next to it in the UI, indicating that the item is protected.
+
+![Screenshot of Recently Created sign](../reference/images/protected-entity-sign.png)
+
+### Example: Rendering an Entity Sign with Custom Logic
+
+The following Sign appears next to any document created within the past week. This Sign isn’t controlled by server flags.
+
+```typescript
+import type { UmbExtensionManifest } from "@umbraco-cms/backoffice/extension-registry";
+import { UMB_DOCUMENT_ENTITY_TYPE } from "@umbraco-cms/backoffice/document";
+
+export const manifests: UmbExtensionManifest = {
+    type: "entitySign",
+    kind: "icon",
+    alias: "Umb.EntitySign.Document.RecentlyCreated",
+    name: "Recently Created Document Sign",
+    forEntityTypes: [UMB_DOCUMENT_ENTITY_TYPE],
+    element: () => import("./recently-created-sign.element.ts"),
+    meta: {
+        iconName: "icon-umbraco",
+        label: "Recently Created",
+    },
+};
+```
+
+And in `recently-created-sign.element.ts`:
+
+```typescript
+@customElement("umb-recently-created-sign")
+export class UmbRecentlyCreatedSignElement extends UmbLitElement {
+    @state() private _createDate?: string;
+
+    override connectedCallback(): void {
+        super.connectedCallback();
+        this.consumeContext(UMB_TREE_ITEM_CONTEXT, (ctx) => {
+            const item = ctx?.getTreeItem?.() ?? (ctx as any).item;
+            this._createDate = item?.createDate;
+            this.requestUpdate();
+        });
+    }
+
+    protected override render() {
+        if (!this._createDate) return null;
+        const created = new Date(this._createDate);
+        const weekAgo = new Date();
+        weekAgo.setDate(weekAgo.getDate() - 7);
+        return created > weekAgo ? html`<div>New</div>` : null;
+    }
+}
+```
+
+![Screenshot of Recently Created sign](../reference/images/custom-entity-sign.png)
+
 {% hint style="info" %}
-The client extension for backoffice signs will be available in Umbraco 16.4 / 17.0.
+Client extensions for backoffice signs are available in Umbraco version 16.4.
 {% endhint %}
-