Fix or remove broken links

Author: sofietoft

13/umbraco-cms/.gitbook.yaml

@@ -11,3 +11,4 @@ redirects:
     extending/packages/types-of-packages: extending/packages/README.md
     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

13/umbraco-cms/extending/embedded-media-providers.md

@@ -131,7 +131,7 @@ If your third-party media provider lacks OEmbed support or requires custom HTML
 
 ### Custom Embed Provider Example
 
-Azure Media Services [(https://azure.microsoft.com/en-gb/services/media-services/)](https://azure.microsoft.com/en-gb/services/media-services/) provide 'broadcast-quality' video streaming services. You can embed the Azure Media Player into your site to play a video [using an IFrame](https://ampdemo.azureedge.net/azuremediaplayer.html).
+Azure Media Services [(https://azure.microsoft.com/en-gb/services/media-services/)](https://azure.microsoft.com/en-gb/services/media-services/) provide 'broadcast-quality' video streaming services. You can embed the Azure Media Player into your site to play a video using an IFrame.
 
 You can create a custom `EmbedProvider` to embed an IFrame video player in your content. This can be done by taking the Media asset URL and writing out the required markup.
 

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

@@ -78,7 +78,7 @@ To read about how you render variant content in Templates, check out the [render
 Culture and hostnames must be added to your language sites before the content can be tested for variants:
 
 1. Right-click the Home node and select **Culture and hostnames...**.
-2. Add a specific URL per language and save. For eg: An English language variant with English (United States) as the language can be given a specific URL [_https://yourwebsite.com/en-us_](https://yourwebsite.com/en-us) and a Danish language variant can be given a specific URL [_https://yourwebsite.com/dk_](https://yourwebsite.com/dk).
+2. Add a specific URL per language and save. For eg: An English language variant with English (United States) as the language can be given a specific URL `https://yourwebsite.com/en-us` and a Danish language variant can be given a specific URL `https://yourwebsite.com/dk`.
 
 The Info content app should now show specific URLs for your language variants.
 

13/umbraco-cms/fundamentals/code/subscribing-to-notifications.md

@@ -194,13 +194,13 @@ Learn more about registering dependencies in the [Dependency Injection](../../re
 1. Access the Umbraco backoffice and publish a piece of content.
 2. Check the log messages in the **Log Viewer** under the **Settings** section.
 
-    ![Log Viewer](images/log-viewer-v14.png)
+    ![Log Viewer](images/log-viewer.png)
 
 3. Search **All Logs**.
 
 If everything is set up correctly you will see your custom log messages.
 
-![Messages in Log](images/log-messages-v14.png)
+![Messages in Log](images/log-messages.png)
 
 ## Additional Notes
 

13/umbraco-cms/fundamentals/design/templates/razor-cheatsheet.md

@@ -8,7 +8,7 @@ They have been called a few names in the past, many people still know Azure Web
 
 > App Service is a fully Managed Platform for professional developers that brings a rich set of capabilities to web, mobile and integration scenarios. Quickly create and deploy mission critical web Apps that scale with your business by using Azure App Service.
 
-[You can read more about them here](https://azure.microsoft.com/en-us/documentation/articles/app-service-web-overview/)
+[You can read more about them here](https://learn.microsoft.com/en-us/azure/app-service/)
 
 Umbraco will run on Azure Web Apps but there are some configuration options and specific Azure Web Apps environment limitations to be aware of.
 

13/umbraco-cms/fundamentals/setup/server-setup/azure-web-apps.md

@@ -39,7 +39,7 @@ When an instance of Umbraco starts up it generates some 'temporary' files on dis
 }
 ```
 
-#### Host synchronization
+### Host synchronization
 
 Umbraco runs within a [.NET Host](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/host/generic-host?view=aspnetcore-6.0).
 

13/umbraco-cms/fundamentals/setup/server-setup/load-balancing/azure-web-apps.md

@@ -972,8 +972,6 @@ Version 7.7.0 introduces User Groups, better user management, and security facil
 
 We are now by default using the e-mail address and not the username for the credentials. When trying to login to the backoffice you need to use the e-mail address as opposed to the username. If you do an upgrade from an older version and would like to keep using the username, change the `<usernameIsEmail>true</usernameIsEmail>` setting to **false**.
 
-For a full list of breaking changes see: [the list on the issue tracker](https://issues.umbraco.org/issues/?q=\&project=U4\&tagValue=\&release=7.7.0\&issueType=\&search=search)
-
 Version 7.7.2 no longer ships with the `CookComputing.XmlRpcV2` assembly. If you reference this assembly or have a package that requires this assembly, you need to copy it back into your website.
 
 This version also ships with far fewer client files that were only relevant for older versions of Umbraco (i.e. < 7.0.0). There might be some packages that were referencing these old client files. If you see missing image references you may need to contact the vendor of the package in question to update their references.
@@ -1051,8 +1049,6 @@ Follow the [**upgrade guide for Umbraco 7**](minor-upgrades-for-umbraco-7.md) to
 
 <summary>7.4.0 to 7.6.0</summary>
 
-Find a list of all the breaking changes below and [a list of the items is also available on the tracker](http://issues.umbraco.org/issues/U4?q=Due+in+version%3A+7.6.0+Backwards+compatible%3F%3A+No+)
-
 The three most important things to note are:
 
 1. In web.config do not change `useLegacyEncoding` to `false` if it is currently set to `true` - changing the password encoding will cause you not being able to log in any more.
@@ -1063,35 +1059,35 @@ The three most important things to note are:
 
 **Dependencies**
 
-**UrlRewriting.Net (**[**U4-9004**](https://issues.umbraco.org/issue/U4-9004)**)**
+**UrlRewriting.Net**
 
 `UrlRewriting` was old, leaking memory, and slowing down website startup when dealing with more than a few rules. It's entirely replaced by the [IIS Url Rewrite](https://www.iis.net/downloads/microsoft/url-rewrite) extension.
 
-**Json.Net (**[**U4-9499**](https://issues.umbraco.org/issue/U4-9499)**)**
+**Json.Net**
 
 Json.Net has been updated to version 10.0.0 to benefit from improvements in features, fixes, and performances (see [release notes](https://github.com/JamesNK/Newtonsoft.Json/releases)). This might be a breaking change for people relying on one of the changed functionality.
 
-**Log4net (**[**U4-1324**](https://issues.umbraco.org/issue/U4-1324)**)**
+**Log4net**
 
 Umbraco has used a custom build of an old (1.2.11) version of log4net that supported Medium Trust. However, Umbraco itself does not support Medium Trust anymore, and therefore log4net has been upgraded to the standard, latest build of log4net 2.0.8.
 
-**ImageProcessor (**[**U4-8963**](https://issues.umbraco.org/issue/U4-8963)**)**
+**ImageProcessor**
 
 An optional parameter has been added to the `GetCropUrl` method in order to support the background color parameter. This breaks the method signature and therefore might require a recompile of user's code.
 
-**HtmlAgilityPack (**[**U4-9655**](https://issues.umbraco.org/issue/U4-9655)**)**
+**HtmlAgilityPack**
 
 The HtmlAgilityPack has been upgraded to version 1.4.9.5. The Umbraco upgrade process should take care of setting up the binding redirects appropriately.
 
 **Core**
 
-**Membership Provider Encoding (**[**U4-6566**](https://issues.umbraco.org/issue/U4-6566)**)**
+**Membership Provider Encoding**
 
 The Membership Provider `useLegacyEncoding` setting is now `false` by default, as the legacy password encoding has weaknesses.
 
 This change only impacts new installs (no change for upgrades).
 
-**Property Value Converters (**[**U4-7318**](https://issues.umbraco.org/issue/U4-7318)**)**
+**Property Value Converters**
 
 A large amount of property value converters contributed by the community have been merged in and are now the default value converters. These converters change the object types returned by `GetPropertyValue` for more convenient types.
 
@@ -1101,29 +1097,29 @@ This change only impacts new installs (no change for upgrades).
 
 The new property value converters are controlled by an `umbracoSettings.config` setting. In the section `settings/content`, setting `EnablePropertyValueConverters` needs to be present and `true` to activate them.
 
-**Database (**[**U4-9201**](https://issues.umbraco.org/issue/U4-9201)**)**
+**Database**
 
 Umbraco has been using a PetaPoco-managed `UmbracoDatabase` instance since version 7 came out. We realized that some of our legacy code still bypassed that mechanism and used parallel, out-of-band database connections, causing issues with transactions.
 
 The legacy code has been refactored to rely on the `UmbracoDatabase` instance. However, because that database is disposed of during `EndRequest`, the code that ran after it has been disposed may not work anymore. This should then be updated to use either an `HttpModule` event that occurs before `EndRequest` or the new `UmbracoModule.EndRequest` event.
 
 More details are available on [issue 146](https://github.com/kipusoep/UrlTracker/issues/146) on the 301 Redirect Tracker GitHub issue tracker.
 
-**Scopes (**[**U4-9406**](https://issues.umbraco.org/issue/U4-9406)**)**
+**Scopes**
 
 Version 7.6 introduces the notion of _scopes_, which allow for wrapping multiple service-level operations in one single transaction. The scopes API is partially public. Scopes are not meant for public use at this stage and we need a few more releases to ensure that the APIs are stable.
 
 Scopes _should not_ change how Umbraco functions.
 
 Introducing scopes means that some public APIs signatures are changing. Most of these changes target internal and/or non-breaking APIs (as per our [guidelines](https://our.umbraco.com/Documentation/Development-Guidelines/breaking-changes)). This should therefore have no impact on sites but may break unit tests.
 
-**Property Editors storing UDI instead of ID (**[**U4-9310**](https://issues.umbraco.org/issue/U4-9310)**)**
+**Property Editors storing UDI instead of ID**
 
 The property editors for pickers for content, media, members, and related links have been updated to store UDI instead of the node ID. Pickers in sites being upgraded have been marked as obsolete but will continue to work as they always did.
 
 New sites will have the obsolete pickers filtered out from the list of available property editors, but they can be enabled by a configuration flag.
 
-**Rich Text Editor (RTE) Images attributes (**[**U4-6228**](https://issues.umbraco.org/issue/U4-6228)**,** [**U4-6595**](http://issues.umbraco.org/issue/U4-6595)**)**
+**Rich Text Editor (RTE) Images attributes**
 
 For a long time, we had a `rel` attribute on an `<img>` tag when inserted into the RTE. This is invalid HTML markup. We worked around this by stripping this attribute using a Property Editor Value converter. Some developers relied on this attribute so we didn't change it to a "data-id" attribute which would have been valid. In 7.6 we are not storing integer IDs in these attributes. Instead of storing UDI values so with this change we no longer use `rel` or `data-id` and instead there will be a "data-udi" attribute. This change should affect only a small amount of people that were previously relying on the values from the "rel" attribute.
 
@@ -1197,7 +1193,7 @@ For manual upgrades:
 * Copy the new folder `~/App_Plugins/ModelsBuilder` into the site
 * Do not forget to merge `~/Config/trees.config` and `~/Config/Dashboard.config` - they contain new and updated entries that are required to be there
   * If you forget `trees.config` you will either not be able to browse the Developer section or you will be logged out immediately when trying to go to the developer section
-* You may experience an error saying `Invalid object name 'umbracoUser'` - this can be fixed by [clearing your cookies on localhost](http://issues.umbraco.org/issue/U4-8031)
+* You may experience an error saying `Invalid object name 'umbracoUser'` - this can be fixed by clearing your cookies on localhost
 
 Follow the [**upgrade guide for Umbraco 7**](minor-upgrades-for-umbraco-7.md) to complete the upgrade.
 

13/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md

@@ -42,7 +42,6 @@ You should re-generate the XML cache. This can be done by following the prompts
 It is recommended that you use a Diff tool to compare the configuration file changes with your own current configuration files.
 
 * `/web.config` updates
-  * Details are listed here: [https://issues.umbraco.org/issue/U4-2900](https://issues.umbraco.org/issue/U4-2900)
   * You will need to compare the new Umbraco 7 `web.config` with your current `web.config`. Here is a quick reference of what needs to change:
     * Remove the `section name="BaseRestExtensions"` section
     * Remove the `section name="FileSystemProviders"` section
@@ -65,11 +64,10 @@ It is recommended that you use a Diff tool to compare the configuration file cha
 * New `macroscripts/web.config`
 * `config/umbracoSettings.config`
   * Umbraco is now shipped with minimal settings but the [full settings](https://our.umbraco.com/documentation/Using-Umbraco/Config-files/umbracoSettings/) are still available
-  * `umbracoSettings` is now a true ASP.NET configuration section [https://issues.umbraco.org/issue/U4-58](https://issues.umbraco.org/issue/U4-58)
+  * `umbracoSettings` is now a true ASP.NET configuration section
   * Remove the `EnableCanvasEditing` element
   * Remove the `webservices` element
 * Removed `xsltExtensions.config`
-  * [https://issues.umbraco.org/issue/U4-2742](https://issues.umbraco.org/issue/U4-2742)
 * `/config/applications.config` and `/config/trees.config` have some icon paths and names updated. You need to merge the new changes into your existing config files.
 * `/config/tinyMceConfig.config`
   * The `inlinepopups` is compatible and supported in Umbraco 7. You need to remove these elements: `plugin loadOnFrontend="true"`, `inlinepopups/plugin`;
@@ -136,11 +134,6 @@ Custom legacy parameters can be mapped to new Umbraco 7 parameter editor aliases
 
 All database changes will be taken care of during the upgrade installation process.
 
-For database change details see (including all child tasks):
-
-* [Issue U4-2886](https://issues.umbraco.org/issue/U4-2886)
-* [Issue U4-3015](https://issues.umbraco.org/issue/U4-3015)
-
 ## Tags
 
 See above for the database updates made for better tag support.

13/umbraco-cms/fundamentals/setup/upgrading/version-specific/upgrade-to-umbraco-7.md

@@ -7,7 +7,6 @@ Many web sites and web applications use a form of load indicator to indicate a b
 Umbraco internally does this via the `<umb-load-indicator />` directive, which you can also use in your own views for the backoffice.
 
 * [`<umbLoadIndicator />` in the **API documentation**](https://apidocs.umbraco.com/v12/ui/#/api/umbraco.directives.directive:umbLoadIndicator)
-* [`<umbLoadIndicator />` source code on **GitHub**](https://github.com/umbraco/Umbraco-CMS/blob/v8/contrib/src/Umbraco.Web.UI.Client/src/common/directives/components/umbloadindicator.directive.js)
 
 The directive doesn't have any parameters on it's own. Since you most likely only wish to show the load indicator during certain states of your code, you can control this either through `ng-if` or `ng-show`.