Cherry pick v16 changes to v17

Author: eshanrnh

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.

16/umbraco-cms/customizing/extending-overview/extension-types/README.md

@@ -23,7 +23,7 @@ The `backofficeEntryPoint` extension type is used to execute JavaScript upon ini
 
 ### [Block Custom View](block-custom-view.md)
 
-The `blockEditorCustomView` extension type is used to define a custom web component for representing blocks inside the Umbraco block grid property editor.
+The `blockEditorCustomView` extension type is used to define a custom web component for representing blocks inside the Umbraco block property editor.
 
 ### [Bundle](bundle.md)
 
@@ -94,6 +94,7 @@ The `tree` extension type is used to create a hierarchical structure composed of
 The `workspace` extension type provides functionality that operates within specific workspace environments, such as document editing, media management, or member editing.
 
 ### [Property Editor UIs](../../../reference/property-editor-uis/README.md)
+
 The `PropertyEditorUi` extension type allows you to create custom property editors in the Umbraco backoffice.
 See the [guide on how to work with and create property editors](../../../customizing/property-editors/README.md) for more information on how to implement this type of extension.
 

16/umbraco-commerce/key-concepts/payment-providers.md

@@ -36,6 +36,7 @@ public class MyPaymentProviderSettings
 All Payment Providers inherit from a base class `AsyncPaymentProviderBase<TSettings>`. `TSettings` is the type of a Plain Old Class Object (POCO) model class representing the Payment Provider's settings. The class must be decorated with `PaymentProviderAttribute` which defines the Payment Providers `alias`.
 
 ### Payment Provider Settings
+
 The settings class consists of a series of properties, each decorated with a `PaymentProviderSettingAttribute`. These attributes are used to dynamically build an editor interface for the settings in the backoffice.
 
 Labels and descriptions for providers and their settings are controlled through [Localization](#localization) entries.
@@ -72,7 +73,7 @@ Generally, there are three methods within a Payment Provider that you may need t
 
 * **GenerateFormAsync** - The `GenerateFormAsync` method generates an HTML form that will redirect the customer to the given payment gateway payment form. In this method you may need to communicate with the payment gateway to initialize a payment, letting the payment gateway know how much to capture. This often results in some kind of code or redirect URL being returned which will need to be embedded into the generated form. The form appears on a checkout **Review** page before payment, featuring a **Continue to Payment** button to submit the form and redirect to the gateway.
 * **ProcessCallbackAsync** - The `ProcessCallbackAsync` method handles the response coming back from the payment gateway and processing whether the payment was successful or not. This can occur _synchronously_, if the payment gateway sends information back during the confirmation page redirect. It can also occur _asynchronously_ if the payment gateway sends the information back via an out-of-band webhook request.
-* **GetOrderReferenceAsync** - The `GetOrderReferenceAsync` method extracts an order reference number from a request when a payment gateway uses an asynchronous webhook to finalize an order.  This method is specifically used where the payment gateway uses a global webhook URL strategy for all notifications rather than a notification URL per transaction. Where a webhook URL can be passed per transaction, then Umbraco Commerce provides a unique callback URL that identifies the order reference as part of the URL parameters. When using the per transaction URL provided, implementing this method becomes unnecessary.
+* **GetOrderReferenceAsync** - The `GetOrderReferenceAsync` method extracts an order reference number from a request when a payment gateway uses an asynchronous webhook to finalize an order. This method is specifically used where the payment gateway uses a global webhook URL strategy for all notifications rather than a notification URL per transaction. Where a webhook URL can be passed per transaction, then Umbraco Commerce provides a unique callback URL that identifies the order reference as part of the URL parameters. When using the per transaction URL provided, implementing this method becomes unnecessary.
 
 _\* denotes a required method implementation_.
 

16/umbraco-commerce/key-concepts/shipping-providers.md

@@ -36,6 +36,7 @@ public class MyShippingProviderSettings
 All Shipping Providers inherit from a base class `ShippingProviderBase<TSettings>`. `TSettings` is the type of a Plain Old Class Object (POCO) model class representing the Shipping Provider's settings. The class must be decorated with `ShippingProviderAttribute` which defines the Shipping Providers `alias`.
 
 ### Shipping Provider Settings
+
 The settings class consists of a series of properties, each decorated with a `ShippingProviderSettingAttribute`. These attributes are used to dynamically build an editor interface for the settings in the backoffice.
 
 Labels and descriptions for providers and their settings are controlled through [Localization](#localization) entries.
@@ -56,11 +57,11 @@ public class MyShippingProviderSettings
     ...
 }
 ```
+
 ## Shipping Provider Responsibilities
 
 The responsibilities of a Shipping Provider are:
 
-
 * **Realtime Rates** - Calculating shipping rate options for a given Order.
 
 ### Realtime Rates

16/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 COLUMNSTORE 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,8 +51,7 @@ 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 COLUMNSTORE 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.

17/umbraco-cms/customizing/extending-overview/extension-types/README.md

@@ -93,6 +93,11 @@ The `tree` extension type is used to create a hierarchical structure composed of
 
 The `workspace` extension type provides functionality that operates within specific workspace environments, such as document editing, media management, or member editing.
 
+### [Property Editor UIs](../../../reference/property-editor-uis/README.md)
+
+The `PropertyEditorUi` extension type allows you to create custom property editors in the Umbraco backoffice.
+See the [guide on how to work with and create property editors](../../../customizing/property-editors/README.md) for more information on how to implement this type of extension.
+
 ## Even More Extension Types
 
 ### [Property Level UI Permissions](../../property-level-ui-permissions.md)
@@ -196,4 +201,3 @@ These are the current types of UI Extensions:
 | workspaceContext        | A workspace context is a context instance that is available to all components in the workspace. It is used to share state between components and to provide a way to communicate between components. Read more about [Workspace Context](./workspaces/workspace-context.md).                                                     |
 | workspaceFooterApp      | A workspace footer app is a component that can be added to the workspace footer.                                                                                                                                                                                                                                                                                  |
 | workspaceView           | A workspace view is a view that can be added to a workspace. It is displayed in the main content area of the workspace. More than one view can be added to a workspace, and the user can switch between them. In that case, the views are displayed as tabs. Read more about [Workspace Views](./workspaces/workspace-views.md). |
-

17/umbraco-cms/customizing/extending-overview/extension-types/block-custom-view.md

@@ -8,11 +8,17 @@ The Block Custom View extension type lets you define a Web Component for represe
 
 ## Build a Custom View
 
+{% hint style="info" %}
+Before creating a Block Custom View, make sure you are familiar with the [Extension Registry in Umbraco](../../../customizing/extending-overview/extension-registry/register-extensions.md).
+You can also refer to the tutorial [Custom Views for Block List](../../../tutorials/creating-custom-views-for-blocklist.md) for a step-by-step guide. 
+{% endhint %}
+
 1. Make a Document Type with a Property using a Block Editor of choice.
 2. Configure at least one Block Type on the Block Editor.
 3. Ensure the Element Type of the Blocks Content Model has a property using `headline` as the Property Alias.
 4. Take note of the Element Type Alias as you will use that in the next step.
-5. Add the following code to the `umbraco-package.json` file:
+5. Create a Settings Model for the above Element Type and add a property with alias `theme`.
+6. Add the following code to the `umbraco-package.json` file:
 
 {% code title="umbraco-package.json" %}
 ```json
@@ -21,15 +27,16 @@ The Block Custom View extension type lets you define a Web Component for represe
   "name": "My.CustomViewPackage",
   "version": "0.1.0",
   "extensions": [
-    {
-      "type": "blockEditorCustomView",
-      "alias": "my.blockEditorCustomView.Example",
-      "name": "My Example Custom View",
-      "element": "/App_Plugins/welcome-dashboard/dist/example-block-custom-view.js",
-      "forContentTypeAlias": "{Insert Element Type Alias here}"
-    }
+	{
+	  "type": "blockEditorCustomView",
+	  "alias": "my.blockEditorCustomView.Example",
+	  "name": "My Example Custom View",
+	  "element": "/App_Plugins/block-custom-view/dist/example-block-custom-view.js",
+	  "forContentTypeAlias": "myElementTypeAlias", // insert element type alias here
+	  "forBlockEditor": "block-list" // insert block type(s) here
+	}
   ]
-
+}
 ```
 {% endcode %}
 
@@ -48,10 +55,14 @@ export class ExampleBlockCustomView extends UmbElementMixin(LitElement) implemen
 	@property({ attribute: false })
 	content?: UmbBlockDataType;
 
+	@property({ attribute: false })
+	settings?: UmbBlockDataType;
+
 	render() {
 		return html`
 			<h5>My Custom View</h5>
 			<p>Headline: ${this.content?.headline}</p>
+			<p>Theme: ${this.settings?.theme}</p>
 		`;
 	}
 

17/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/file-upload.md

@@ -22,7 +22,7 @@ Find the full documentation for the property in the [Media Picker](media-picker-
 
 ## Content Example
 
-![Content Example Empty](../../../../../../16/umbraco-cms/fundamentals/backoffice/property-editors/built-in-property-editors/images/content-example-empty.png) ![Content Example](../../../../../../16/umbraco-cms/fundamentals/backoffice/property-editors/built-in-property-editors/images/File-Upload-content-example.png)
+![Content Example Empty](images/fileupload-content-empty.png) ![Content Example](images/fileupload-content.png)
 
 In code, the property is a string, which references the location of the file.
 
@@ -33,42 +33,36 @@ Example: `"/media/o01axaqu/guidelines-on-remote-working.pdf"`
 ### Without Models Builder
 
 ```csharp
-@using System.IO;
-@{
-    if (Model.HasValue("myFile"))
-    {
-        var myFile = Model.Value<string>("myFile");
-
-        <a href="@myFile">@System.IO.Path.GetFileName(myFile)</a>
-    }
+@if (Model.HasValue("myFile"))
+{
+    var myFile = Model.Value<string>("myFile");
 
+    <a href="@myFile">@System.IO.Path.GetFileName(myFile)</a>
 }
 ```
 
 ### With Models Builder
 
 ```csharp
-@if (!Model.HasValue(Model.MyFile))
+@if (Model.HasValue("myFile"))
 {
    <a href="@Model.MyFile">@System.IO.Path.GetFileName(Model.MyFile)</a>
 }
 ```
 
 ## Add values programmatically
 
-{% hint style="info" %}
-The samples in this section have not been verified against the latest version of Umbraco.
-
-Instead, we recommend using the [Media Picker](media-picker-3.md) for uploading files to your Umbraco website.
-{% endhint %}
-
 See the example below to see how a value can be added or changed programmatically. To update a value of this property editor you need the [Content Service](https://apidocs.umbraco.com/v15/csharp/api/Umbraco.Cms.Core.Services.ContentService.html) and the [Media Service](https://apidocs.umbraco.com/v15/csharp/api/Umbraco.Cms.Core.Services.MediaService.html).
 
 {% hint style="info" %}
 The example below demonstrates how to add values programmatically using a Razor view. However, this is used for illustrative purposes only and is not the recommended method for production environments.
 {% endhint %}
 
 ```csharp
+@using System.Net
+@using Umbraco.Cms.Core
+@using Umbraco.Cms.Core.Services
+@using Umbraco.Cms.Core.PropertyEditors
 @using Umbraco.Cms.Core.IO
 @using Umbraco.Cms.Core.Serialization
 @using Umbraco.Cms.Core.Strings
@@ -115,15 +109,6 @@ The example below demonstrates how to add values programmatically using a Razor
 }
 ```
 
-Although the use of a GUID is preferable, you can also use the numeric ID to get the page:
-
-```csharp
-@{
-    // Get the page using it's id
-    var content = ContentService.GetById(1234); 
-}
-```
-
 If Models Builder is enabled you can get the alias of the desired property without using a magic string:
 
 ```csharp