Merge branch 'umbraco:main' into main

Author: bszyman

10/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/nested-content.md

@@ -4,6 +4,8 @@
 We highly recommend that you use the [Block List](block-editor/block-list-editor.md) instead.
 
 Nested Content has been marked as obsolete and development on the property editor has been discontinued.
+
+[Umbraco Deploy](https://docs.umbraco.com/umbraco-deploy/deployment-workflow/import-export/import-with-migrations) and [uSync migrations](https://github.com/Jumoo/uSyncMigrations) have support for migrating from nested content to the block list.
 {% endhint %}
 
 `Alias: Umbraco.NestedContent`
@@ -106,7 +108,7 @@ Example:
             // Render your content, e.g. item.Value<string>("heading")
         }
     }
-    
+
 }
 ```
 
@@ -176,31 +178,31 @@ Afterwards, the entire list needs to be serialized to Json via JsonConvert.
 @using Newtonsoft.Json;
 @inject IContentService _contentService;
 
- //if the class containing our code inherits SurfaceController, UmbracoApiController, 
+ //if the class containing our code inherits SurfaceController, UmbracoApiController,
  //or UmbracoAuthorizedApiController, we can get ContentService from Services namespace
- var contentService = _contentService; 
+ var contentService = _contentService;
 //here we create a new node, and fill out attendeeList afterwards
- IContent request = contentService.Create("new node", guid, "mydoctype", -1); 
+ IContent request = contentService.Create("new node", guid, "mydoctype", -1);
  //our list which will contain nested content
- var attendees = new List<Dictionary<string, string>>(); 
+ var attendees = new List<Dictionary<string, string>>();
 //participants is our list of attendees - multiple items, good use case for nested content
- foreach (var person in participants) 
+ foreach (var person in participants)
             attendees.Add(new Dictionary<string, string>() {
             //this is the only "default" value we need to fill for nested item
-            {"ncContentTypeAlias","attendee"}, 
+            {"ncContentTypeAlias","attendee"},
             {"user_name", person.name},
             {"user_email",person.user_email},
-            {"join_time",person.join_time.ToString()}, 
+            {"join_time",person.join_time.ToString()},
             //we convert some properties to String just to be on the safe side
             {"leave_time",person.leave_time.ToString()},
             {"duration",person.duration.ToString()},
             {"phone",person.phone.ToString()}
             });
             }
             //bind the attendees List to attendeeList property on the newly created content node
-            request.SetValue("attendeeList", JsonConvert.SerializeObject(attendees)); 
+            request.SetValue("attendeeList", JsonConvert.SerializeObject(attendees));
             //Save the entire node via ContentService
-            ContentService.SaveAndPublish(request); 
+            ContentService.SaveAndPublish(request);
 ```
 
 In the above sample we iterate through a list of participants (the data for such participants could be coming from an API, for example), and add a new `Dictionary` item for each person in the list.

10/umbraco-cms/reference/configuration/contentsettings.md

@@ -13,7 +13,7 @@ The following snippet will give an overview of the keys and values in the conten
         "KeepAllVersionsNewerThanDays": 7,
         "KeepLatestVersionPerDayForDays": 90
       },
-      "AllowEditInvariantFromNonDefault": true,
+      "AllowEditInvariantFromNonDefault": false,
       "AllowedUploadFiles": [],
       "AllowedMediaHosts":  [],
       "DisableDeleteWhenReferenced": false,
@@ -60,9 +60,9 @@ In the root level section, that is those without a seperate sub section like Ima
 
 Invariant properties are properties on a multilingual site that are not varied by culture. This means that they share the same value across all languages added to the website.
 
-When the setting is set to `false` the invariant properties that are shared between all languages can only be edited from the default language. This means you need access to the default language, in order to edit the property.
+When the setting is set to `false` (default) the invariant properties that are shared between all languages can only be edited from the default language. This means you need access to the default language, in order to edit the property.
 
-When set to `true` (default) the invariant properties will need to be unlocked before they can be edited. The lock exists in order to make it clear that this change will affect more languages.
+When set to `true` the invariant properties will need to be unlocked before they can be edited. The lock exists in order to make it clear that this change will affect more languages.
 
 ### Allowed upload files
 

10/umbraco-workflow/installation/licensing.md

@@ -40,6 +40,14 @@ Once you have received your license code it needs to be installed on your site.
 }
 ```
 
+{% hint style="info" %}
+You might run into issues when using a period in the product name when using environment variables. Use an underscore in the product name instead, to avoid problems.
+
+```json
+"Umbraco_Workflow": "YOUR_LICENSE_KEY"
+```
+{% endhint %}
+
 ### Verify the license installation
 
 You can verify that your license is successfully installed by logging into your project's backoffice and navigating to the settings section. Here you will see a licenses dashboard which should display the status of your license.

13/umbraco-cms/.gitbook.yaml

@@ -12,3 +12,4 @@ redirects:
     extending/property-editors/build-a-block-editor: fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/README.md
     tutorials/creating-and-distributing-a-package: extending/packages/creating-a-package.md
     fundamentals/design/templates/razor-cheatsheet: fundamentals/design/templates/README.md
+    reference/management-api: reference/dive-into-the-code.md

13/umbraco-cms/SUMMARY.md

@@ -368,6 +368,7 @@
 * [Cache & Distributed Cache](reference/cache/README.md)
   * [Accessing the cache](reference/cache/application-cache.md)
   * [ICacheRefresher](reference/cache/icacherefresher.md)
+  * [IMemberPartialViewCacheInvalidator](reference/cache/imemberpartialviewcacheinvalidator.md)
   * [IServerMessenger](reference/cache/iservermessenger.md)
   * [Getting/Adding/Updating/Inserting Into Cache](reference/cache/updating-cache.md)
   * [Examples](reference/cache/examples/README.md)

13/umbraco-cms/extending/packages/example-package-repository.md

@@ -30,7 +30,7 @@ When the next major version of Umbraco is released, we'll test and either extend
 
 ### Tests Project
 
-We have a [project for unit tests](https://github.com/umbraco/Umbraco.AuthorizedServices/tree/main/tests/Umbraco.AuthorizedServices.Tests) in `tests/<ProjectName>.Tests`.  It contains references to `Umbraco.Cms.Tets` and a project reference to the package:
+We have a [project for unit tests](https://github.com/umbraco/Umbraco.AuthorizedServices/tree/main/tests/Umbraco.AuthorizedServices.Tests) in `tests/<ProjectName>.Tests`.  It contains references to `Umbraco.Cms.Tests` and a project reference to the package:
 
 ```xml
 <ProjectReference Include="..\..\src\Umbraco.AuthorizedServices\Umbraco.AuthorizedServices.csproj" />

13/umbraco-cms/fundamentals/backoffice/variants.md

@@ -66,8 +66,6 @@ Each Property Editor that does not allow variants (an Invariant Property) will b
 {% hint style="info" %}
 Whether or not the lock is enabled on the invariant properties depends on the `AllowEditInvariantFromNonDefault` setting in the `appsettings.json` file.
 
-For projects created on Umbraco version 10.2 or later, the setting is `true`, by default. If the project is upgraded to version 10.2 or later, the setting will by default be `false`.
-
 Learn more about the `AllowEditInvariantFromNonDefault` setting in the [Security Settings](../../reference/configuration/securitysettings.md) article.
 {% endhint %}
 

13/umbraco-cms/reference/cache/imemberpartialviewcacheinvalidator.md

@@ -0,0 +1,37 @@
+# Partial view cache refresher for members
+
+This section describes the `IMemberPartialViewCacheInvalidator` interface, what it's default implementation does and how to customize it.
+
+## What is an IMemberPartialViewCacheInvalidator?
+
+This interface is used to isolate the logic that invalidates parts of the partial view cache when a member is updated.
+
+## Why do we need to partially invalidate the partial view cache?
+
+Razor templates may show data that is retrieved from a member object. Those templates might be cached by using the partial caching mechanism (for example, `@await Html.CachedPartialAsync("member",Model,TimeSpan.FromDays(1), cacheByMember:true)`). When a member is updated, these cached partials must be invalidated to ensure updated data is shown.
+
+## Where is it used?
+
+This interface is called from the member cache refresher (`MemberCacheRefresher`), which is invoked every time a member is updated.
+
+## Details of the default implementation
+
+Razor template partials are cached through a call to `Html.CachedPartialAsync` with `cacheByMember` set to `true`. This will append the ID of the currently logged-in member with a marker to the partial view cache key.  For example, `-m1015-`.
+
+When the `ClearPartialViewCacheItems` method is called it will clear all cache items that match the marker for the updated members.
+
+If no member is logged in during caching, items with an empty member marker (for example, `-m-`) are also cleared.
+
+## Customizing the implementation
+
+You can replace the default implementation by removing it and registering your own in a composer.
+
+```csharp
+public class ReplaceMemberCacheInvalidatorComposer : IComposer
+{
+    public void Compose(IUmbracoBuilder builder)
+    {
+        builder.Services.AddUnique<IMemberPartialViewCacheInvalidator, MyCustomMemberPartialViewCacheInvalidator>();
+    }
+}
+```

13/umbraco-cms/reference/configuration/contentsettings.md

@@ -17,7 +17,7 @@ The following snippet will give an overview of the keys and values in the conten
         "KeepAllVersionsNewerThanDays": 7,
         "KeepLatestVersionPerDayForDays": 90
       },
-      "AllowEditInvariantFromNonDefault": true,
+      "AllowEditInvariantFromNonDefault": false,
       "AllowedMediaHosts":  [],
       "AllowedUploadedFileExtensions": [],
       "DisableDeleteWhenReferenced": false,
@@ -62,9 +62,9 @@ In the root level section, that is those without a separate sub section like Ima
 
 Invariant properties are properties on a multilingual site that are not varied by culture. This means that they share the same value across all languages added to the website.
 
-When the setting is set to `false` the invariant properties that are shared between all languages can only be edited from the default language. This means you need access to the default language, in order to edit the property.
+When the setting is set to `false` (default) the invariant properties that are shared between all languages can only be edited from the default language. This means you need access to the default language, in order to edit the property.
 
-When set to `true` (default) the invariant properties will need to be unlocked before they can be edited. The lock exists in order to make it clear that this change will affect more languages.
+When set to `true` the invariant properties will need to be unlocked before they can be edited. The lock exists in order to make it clear that this change will affect more languages.
 
 ### Allowed upload file extensions
 

13/umbraco-cms/reference/security/external-login-providers.md

@@ -151,6 +151,8 @@ In those cases, it would mean that anyone who has a Google or Facebook account c
 
 If auto-linking for public providers such as these was needed you would need to limit the access. This can be done by domain or other information provided in the claims using the options/callbacks specified in those provider's authentication options.
 
+When auto-linking for the backoffice you will want to define what user groups the user will be part of. This is done via the `defaultUserGroups` parameter provided to the constructor of `ExternalSignInAutoLinkOptions` (see example below). If the value is not set the user will by default be added to the Editors group.
+
 ### Auto-linking on Member authentication
 
 Auto-linking on Member authentication only makes sense if you have a public member registration already or the provider does not have public account creation.