Merge branch 'main' into cms/workspace-extensions

Author: iOvergaard

.github/lychee.toml

@@ -31,15 +31,20 @@ timeout = 10
 retry_wait_time = 1
 
 # Accept more status codes (follow redirects automatically)
-accept = ["200..=204", "301..=308", "429"]
+# Note: 522 and 502 are server errors, not broken links
+accept = [
+  "200..=204", 
+  "301..=308", 
+  "429",
+  "502",  # Bad Gateway
+  "522"   # Connection timed out (Cloudflare)
+]
 
-# Avoid false fragment errors
-include_fragments = false  
+# Don't check fragments/anchors - they cause false positives
+include_fragments = false
 
-# Only test links with the given schemes (e.g. https).
-# Omit to check links with any other scheme.
-# At the moment, we support http, https, file, and mailto.
-scheme = ["https"]
+# Only test links with the given schemes (e.g. https and http)
+scheme = ["https", "http"]
 
 # When links are available using HTTPS, treat HTTP links as errors.
 require_https = false
@@ -54,9 +59,21 @@ exclude = [
   '^mailto:',
   '^https?://localhost',
   '^https?://127\\.0\\.0\\.1',
-  '^https://www\.linkedin\.com',
-  '^https?://issues\.umbraco\.org/',
-  '^https?://web\\.archive\\.org/web/'
+  '^https://www\\.linkedin\\.com',
+  
+  # Exclude all issues.umbraco.org - unreliable and often returns 522
+  'http://issues\\.umbraco\\.org',
+  'https://issues\\.umbraco\\.org',
+  
+  # Exclude umbraco.com blog posts that return errors
+  'https://umbraco\\.com/blog/',
+  
+  # Exclude web archive links
+  'web\\.archive\\.org/web/',
+  
+  # Exclude internal links with version anchors
+  'version-specific#umbraco-',
+  'README\\.md#umbraco-[0-9]',
 ]
 
 # Exclude these filesystem paths from getting checked.
@@ -77,4 +94,4 @@ include_mail = true
 ############################# Content Checks ######################
 # Mark pages as broken if the body contains "page not found" or "404"
 [content]
-deny = ["(?i)page not found", "(?i)404"]
+deny = ["(?i)page not found", "(?i)404"]

.github/workflows/check-broken-pr-links.yml

@@ -1,7 +1,7 @@
 name: Check Links in Pull Requests
 
 on:
-  pull_request:
+  pull_request:           # changed from pull_request
     branches:
       - main
     paths:
@@ -59,21 +59,36 @@ jobs:
             /^Errors in / {
               file=$3
               gsub("^/home/runner/work/UmbracoDocs/UmbracoDocs/", "", file)
-              print "\n**Broken links found in: " file "**" >> "lychee/comment.md"
+              current_file = file
+              has_errors = 0
               next
             }
 
-            /\[ERROR\]/ {
+            /Error: ERROR\]/ {
+              # Skip anchor errors for #umbraco-[number] patterns
+              if ($0 ~ /#umbraco-[0-9]+/) next
+              
+              # Print file header if this is the first error for this file
+              if (current_file != "" && has_errors == 0) {
+                print "\n**Broken links found in: " current_file "**" >> "lychee/comment.md"
+                has_errors = 1
+              }
+              
               msg = $0
-              sub(/^- \[ \] /, "", msg)
-              sub(/^\[ERROR\] /, "", msg)
+              sub(/^Error: ERROR\] /, "", msg)
               gsub("^file:///home/runner/work/UmbracoDocs/UmbracoDocs/", "", msg)
               gsub(/\|/, "\\|", msg)   # escape Markdown pipe
               print "\n⚓ Anchor not found → " msg "\n" >> "lychee/comment.md"
               next
             }
 
             /\[404\]/ {
+              # Print file header if this is the first error for this file
+              if (current_file != "" && has_errors == 0) {
+                print "\n**Broken links found in: " current_file "**" >> "lychee/comment.md"
+                has_errors = 1
+              }
+              
               msg = $0
               sub(/^- \[ \] /, "", msg)
               sub(/^\[404\] /, "", msg)
@@ -83,6 +98,12 @@ jobs:
             }
 
             /\[301\]|\[302\]/ {
+              # Print file header if this is the first error for this file
+              if (current_file != "" && has_errors == 0) {
+                print "\n**Broken links found in: " current_file "**" >> "lychee/comment.md"
+                has_errors = 1
+              }
+              
               msg = $0
               sub(/^- \[ \] /, "", msg)
               sub(/^\[(301|302)\] /, "", msg)
@@ -91,7 +112,49 @@ jobs:
               next
             }
 
+            /\[522\]/ {
+              # Skip 522 errors from issues.umbraco.org
+              if ($0 ~ /issues\.umbraco\.org/) next
+              
+              # Print file header if this is the first error for this file
+              if (current_file != "" && has_errors == 0) {
+                print "\n**Broken links found in: " current_file "**" >> "lychee/comment.md"
+                has_errors = 1
+              }
+              
+              msg = $0
+              sub(/^- \[ \] /, "", msg)
+              sub(/^\[522\] /, "", msg)
+              gsub(/\|/, "\\|", msg)
+              print "\n⚠ Server error (522) → " msg "\n" >> "lychee/comment.md"
+              next
+            }
+
+            /\[502\]/ {
+              # Skip 502 errors from umbraco.com
+              if ($0 ~ /umbraco\.com/) next
+              
+              # Print file header if this is the first error for this file
+              if (current_file != "" && has_errors == 0) {
+                print "\n**Broken links found in: " current_file "**" >> "lychee/comment.md"
+                has_errors = 1
+              }
+              
+              msg = $0
+              sub(/^- \[ \] /, "", msg)
+              sub(/^\[502\] /, "", msg)
+              gsub(/\|/, "\\|", msg)
+              print "\n⚠ Server error (502) → " msg "\n" >> "lychee/comment.md"
+              next
+            }
+
             /Timeout/ && !/Timeouts/ {
+              # Print file header if this is the first error for this file
+              if (current_file != "" && has_errors == 0) {
+                print "\n**Broken links found in: " current_file "**" >> "lychee/comment.md"
+                has_errors = 1
+              }
+              
               msg = $0
               sub(/^- \[ \] /, "", msg)
               gsub(/\|/, "\\|", msg)   # escape pipe just in case
@@ -101,6 +164,12 @@ jobs:
 
             # catch-all for any other errors
             /^\- \[ \] \[[0-9]+\]/ {
+              # Print file header if this is the first error for this file
+              if (current_file != "" && has_errors == 0) {
+                print "\n**Broken links found in: " current_file "**" >> "lychee/comment.md"
+                has_errors = 1
+              }
+              
               msg = $0
               sub(/^- \[ \] /, "", msg)
               gsub(/\|/, "|", msg)
@@ -131,4 +200,4 @@ jobs:
         if: steps.format-report.outputs.has_content == 'true'
         run: |
           echo "❌ Broken links detected. Please review the PR comment for details."
-          exit 1
+          exit 1

10/umbraco-cms/SUMMARY.md

@@ -6,7 +6,7 @@
   * [Umbraco 8 Documentation](https://our.umbraco.com/documentation/)
   * [Umbraco 7 Documentation](https://our.umbraco.com/documentation/)
 * [Release Notes](https://our.umbraco.com/download/releases/)
-* [Contribute](https://docs.umbraco.com/welcome/contribute/getting-started)
+* [Contribute](https://docs.umbraco.com/contributing)
 * [Sustainability Best Practices](https://docs.umbraco.com/sustainability-best-practices/)
 
 ## Fundamentals
@@ -198,7 +198,7 @@
   * [Installing and Uninstalling Packages](extending/packages/installing-and-uninstalling-packages.md)
   * [Maintaining packages](extending/packages/maintaining-packages.md)
   * [Create accessible Umbraco packages](extending/packages/accessibility.md)
-  * [Example Package Repository](./extending/packages/example-package-repository.md)
+  * [Example Package Repository](extending/packages/example-package-repository.md)
 * [UI Library](extending/ui-library.md)
 
 ## Reference

10/umbraco-cms/fundamentals/setup/install/install-umbraco-with-templates.md

@@ -12,7 +12,7 @@ Video tutorial
 
 1. Install the latest [.NET SDK](https://dotnet.microsoft.com/download).
 2. Run `dotnet new install Umbraco.Templates` to install the project templates.\
-    _The solution is packaged up into the NuGet package_ [_Umbraco.Templates_](https://www.nuget.org/packages/Umbraco.Templates) _and can be installed into the dotnet CLI_.
+   &#xNAN;_The solution is packaged up into the NuGet package_ [_Umbraco.Templates_](https://www.nuget.org/packages/Umbraco.Templates) _and can be installed into the dotnet CLI_.
 
 > Once that is complete, you can see that Umbraco was added to the list of available projects types by running `dotnet new --list`:
 

10/umbraco-cms/fundamentals/setup/install/unattended-install.md

@@ -47,7 +47,7 @@ It is recommended that you make use of the values shown below for the `Cache`, `
 ```json
 {
   "ConnectionStrings": {
-    "umbracoDbDSN": "Data Source=|DataDirectory|/Umbraco.sqlite.db;Cache=Private;Foreign Keys=True;Pooling=True",
+    "umbracoDbDSN": "Data Source=|DataDirectory|/Umbraco.sqlite.db;Cache=Shared;Foreign Keys=True;Pooling=True",
     "umbracoDbDSN_ProviderName": "Microsoft.Data.SQLite"
   }
 }

10/umbraco-cms/fundamentals/setup/server-setup/running-umbraco-in-docker.md

@@ -4,33 +4,32 @@ Exactly how you choose to compose your Dockerfile will depend on your project sp
 
 ## What is Docker
 
-Docker is a platform for developing, shipping, and running applications in containers. Multiple services exist for hosting these containers.  For more information, refer to the [official Docker Documentation](https://docs.docker.com/)
+Docker is a platform for developing, shipping, and running applications in containers. Multiple services exist for hosting these containers. For more information, refer to the [official Docker Documentation](https://docs.docker.com/)
 
 ## The Docker file system
 
-By default, files created inside a container are written to an ephemeral, writable container layer. 
+By default, files created inside a container are written to an ephemeral, writable container layer.\
 This means that the files don't persist when the container is removed, and it's challenging to get files out of the container. Additionally, this writable layer is not suitable for performance-critical data processing.
 
 This has implications when running Umbraco in Docker.
 
 For more information, refer to the [Docker documentation on storage](https://docs.docker.com/engine/storage/).
 
-### General file system consideration 
+### General file system consideration
 
 In general, when working with files and Docker you work in a "push" fashion with read-only layers. When you build, you take all your files and "push" them into this read-only layer.
 
 This means that you should avoid making files on the fly, and instead rely on building your image.
 
-In an Umbraco context, this means you should not create or edit template, script or stylesheet files via the backoffice. These should be deployed as part of your web application and not managed via Umbraco. 
+In an Umbraco context, this means you should not create or edit template, script or stylesheet files via the backoffice. These should be deployed as part of your web application and not managed via Umbraco.
 
 Similarly, you shouldn't use InMemory modelsbuilder, since that also relies on creating files on the disk. While this is not a hard requirement, it doesn't provide any value unless you are live editing your site.
 
 Instead, configure models builder to use "source code" mode in development, and "none" in production, as [described when using runtime modes](https://docs.umbraco.com/umbraco-cms/fundamentals/setup/server-setup/runtime-modes).
 
-
 ### Logs
 
-Umbraco writes logs to the `/umbraco/Logs/` directory. Due to the performance implications of writing to a writable layer, 
+Umbraco writes logs to the `/umbraco/Logs/` directory. Due to the performance implications of writing to a writable layer,\
 and the limited size, it is recommended to mount a volume to this directory.
 
 ### Data
@@ -39,18 +38,18 @@ The `/umbraco/Data/` directory is used to store temporary files, such as file up
 
 ### Media
 
-It's recommended to not store media in the writable layer. This is for similar performance reasons as logs, 
-but also for practical hosting reasons. You likely want to persist media files between containers. 
+It's recommended to not store media in the writable layer. This is for similar performance reasons as logs,\
+but also for practical hosting reasons. You likely want to persist media files between containers.
 
 One solution is to use bind mounts. The ideal setup, though, is to store the media and ImageSharp cache externally. For more information, refer to the [Azure Blob Storage documentation](https://docs.umbraco.com/umbraco-cms/extending/filesystemproviders/azure-blob-storage).
 
 ### Required files
 
-Your solution may require some specific files to run, such as license files. You will need to pass these files into the container at build time, or mount them externally. 
+Your solution may require some specific files to run, such as license files. You will need to pass these files into the container at build time, or mount them externally.
 
 ## HTTPS
 
-When running websites in Docker, it's common to do so behind a reverse proxy or load balancer.
+When running websites in Docker, it's common to do so behind a reverse proxy or load balancer.\
 In these scenarios you will likely handle SSL termination at the reverse proxy. This means that Umbraco will not be aware of the SSL termination, and will complain about not using HTTPS.
 
 Umbraco checks for HTTPS in two locations:
@@ -85,7 +84,7 @@ The `UseHttpsValidator` must be removed through code For more information see th
 
 The code to remove the validator can look something like:
 
-```C#
+```c#
 using Umbraco.Cms.Core.Composing;
 using Umbraco.Cms.Infrastructure.Runtime.RuntimeModeValidators;
 

10/umbraco-cms/fundamentals/setup/upgrading/images/upgrade-to-8_1 (1) (1) (1) (1).png

@@ -13,7 +13,7 @@ A content migration tool has been implemented in Umbraco 8.1.0, to help you with
 In this guide you can read more about the tool, its limitations, and how to use it in practice.
 
 {% hint style="info" %}
-#### Migrating Umbraco Cloud sites
+**Migrating Umbraco Cloud sites**
 
 Follow the [steps outlined in the Umbraco Cloud documentation](../../../../../umbraco-cloud/upgrades/migrate-from-umbraco-7-to-8.md) to upgrade your Umbraco 7 site on Cloud.
 {% endhint %}
@@ -71,9 +71,9 @@ There are 3 options that a developer can choose to do to work around this automa
 
 This option requires you to create a custom C# migrator for each of your custom property editors that store custom configuration data. It will also require that you implement these migrators before you run the Umbraco 8 content migration.
 
-To do this, you will create an implementation of `IPreValueMigrator` or inherit from the base class [`DefaultPreValueMigrator`](https://github.com/umbraco/Umbraco-CMS/blob/v8/dev/src/Umbraco.Core/Migrations/Upgrade/V\_8\_0\_0/DataTypes/DefaultPreValueMigrator.cs).
+To do this, you will create an implementation of `IPreValueMigrator` or inherit from the base class [`DefaultPreValueMigrator`](https://github.com/umbraco/Umbraco-CMS/blob/v8/dev/src/Umbraco.Core/Migrations/Upgrade/V_8_0_0/DataTypes/DefaultPreValueMigrator.cs).
 
-There are plenty of examples of this in the [Umbraco-CMS codebase](https://github.com/umbraco/Umbraco-CMS/tree/v8/dev/src/Umbraco.Core/Migrations/Upgrade/V\_8\_0\_0/DataTypes).
+There are plenty of examples of this in the [Umbraco-CMS codebase](https://github.com/umbraco/Umbraco-CMS/tree/v8/dev/src/Umbraco.Core/Migrations/Upgrade/V_8_0_0/DataTypes).
 
 You will then need to register them in a composer:
 
@@ -131,7 +131,7 @@ The site in this example is an Umbraco 7.13.1 site, and we will use Nuget to upd
 
 Following the [general upgrade instructions](../) we will now upgrade via Nuget until we get to this point:
 
-![Upgrading to v7.14](<../images/upgrading-7\_14 (1) (1) (1) (1).png>)
+![Upgrading to v7.14](<../images/upgrading-7_14 (1) (1) (1) (1).png>)
 
 {% hint style="warning" %}
 When upgrading an old website, check if you are using obsolete properties in your Data Types. These should be changed to their updated counterparts. The migration **will fail if you are still using obsolete properties.**
@@ -156,7 +156,7 @@ Once it is upgraded and you have verified everything is working, move on to the
 
 The first thing to do is to spin up a fresh new Umbraco 8.1+ site. Make sure everything works and that no content is there.
 
-![Fresh 8.1 site](<../images/fresh-8\_1-site (1) (1) (1).png>)
+![Fresh 8.1 site](<../images/fresh-8_1-site (1) (1) (1).png>)
 
 {% hint style="warning" %}
 If you have customized the `UsersMembershipProvider` on your Umbraco 7 site you need to copy that over to the 8.1 `web.config` as well. Additionally you need to update the `type` attribute to be `type="Umbraco.Web.Security.Providers.UsersMembershipProvider, Umbraco.Web"`.
@@ -174,11 +174,11 @@ The version will be set to 8.1.0, and you need to change it to the version you a
 
 When you start the site it will ask you to login and then show you this screen:
 
-![Upgrade database to 8.1](<../../../../../../umbraco-cloud/product-upgrades/images/upgrade-to-8\_1 (1) (1).png>)
+![Upgrade database to 8.1](<../images/upgrade-to-8_1 (1) (1) (1).png>)
 
 From here, the automatic migration will take over, and after a little bit you can log in and see your content:
 
-![Content is on 8.1](<../images/content-on-8\_1 (1) (1) (1).png>)
+![Content is on 8.1](<../images/content-on-8_1 (1) (1) (1).png>)
 
 {% hint style="info" %}
 Please be aware that this is a **content migration**. If you go to the frontend after following these steps, it will throw errors.

10/umbraco-cms/fundamentals/setup/upgrading/version-specific/migrate-content-to-umbraco-8.md

@@ -12,14 +12,14 @@ An connection strings config can look like this:
 ```json
 {
   "ConnectionStrings": {
-    "umbracoDbDSN": "Data Source=|DataDirectory|/Umbraco.sqlite.db;Cache=Private;Foreign Keys=True;Pooling=True",
+    "umbracoDbDSN": "Data Source=|DataDirectory|/Umbraco.sqlite.db;Cache=Shared;Foreign Keys=True;Pooling=True",
     "umbracoDbDSN_ProviderName": "Microsoft.Data.SQLite"
   }
 }
 ```
 
 {% hint style="info" %}
-We recommend using private cache for SQLite. You can read more on why shared cache is discouraged in [the official SQLite documentation](https://sqlite.org/sharedcache.html).
+We recommend using shared cache for SQLite when using Umbraco, as it provides better performance and consistency when multiple connections may access the database simultaneously.
 {% endhint %}
 
 The connection string used here is an SQLite connection string, that will connect to a data in the file `Umbraco.sqlite.db` located in `/umbraco/Data` .

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

@@ -35,7 +35,7 @@ Umbraco Cloud uses IIS for hosting. This means you need to add the setting in a
 
 ## Using Kestrel
 
-Runtime settings allow you to configure the `MaxRequestLength` and `MaxQueryStringLength` for kestrel. If you want to upload files larger than 28.6MB, then you have to configure these settings. If nothing is configured requests and query strings can only be the default size and smaller.
+Runtime settings allow you to configure the `MaxRequestLength` and `MaxQueryStringLength` for kestrel. If you want to upload files larger than 50MB, then you have to configure these settings. If nothing is configured requests and query strings can only be the default size and smaller.
 
 An example of a configuration could look something like this: