Describes how to upgrading existing installations to new versions.
In this article, you will find everything you need to upgrade your Umbraco CMS project.
If you are new to upgrades, be sure to read the introduction to upgrades in Umbraco first.
You will find instructions on how to upgrade to a new minor or major version as well as how to run upgrades unattended.
You can upgrade to a new major version of Umbraco CMS directly by using NuGet.
You must upgrade to the closest Long-term Support (LTS) major version before upgrading to the latest version. For Umbraco 10, the closest long-term support version is Umbraco 13. Once the project is on Umbraco 13, you can move on to Umbraco 14.
Switching to a new major version of Umbraco CMS also means switching to a new .NET version. Ensure that any packages used on your site are compatible with this version before upgrading.
The package compatibility can be checked on the package's download page. Locate the Project compatibility area and select View details to check version-specific compatibility.
Choose the correct .NET versionUse the table below to determine which .NET version to upgrade to when going through the steps below.
Upgrade your project using Visual StudioIt's recommended that you upgrade the site offline and test the upgrade fully before deploying it to the production environment.
Stop your site in IIS to prevent any changes from being made while you are upgrading.
Open your Umbraco project in Visual Studio.
Right-click on the project name in the Solution Explorer and select Properties.
Select the .NET version from the Target Framework drop-down.
Go to Tools > NuGet Package Manager > Manage NuGet Packages for Solution...
Go to the Installed tab in the NuGet Package Manager.
Upgrade Umbraco.Cms.
a. Select the correct version from the Version drop-down.
b. Click Install to upgrade your project.
Make sure that your connection string has TrustServerCertificate=True
to complete the upgrade successfully:
"ConnectionStrings": {
"umbracoDbDSN": "Server=YourLocalSQLServerHere;Database=NameOfYourDatabaseHere;User Id=NameOfYourUserHere;Password=YourPasswordHere;TrustServerCertificate=True"
}
Restart your site in IIS, then build and run your project to finish the installation.
Umbraco 13 and later versions use the Minimal Hosting Model .
If you have added custom code to the startup.cs
file, it is recommended to move that code into a Composer after upgrading.
It is necessary to run the upgrade installer on each environment of your Umbraco site. This wil occur on first boot of an upgraded project as it is deployed into a new environment.
Potential issues and gotchasIf you receive an error that a deploy license is missing even though you have a valid license, follow the guide below.
Google Chrome has aggressive caching, so when experiencing startup issues, clear the cache and cookies thoroughly. Ideally, this should be done for other browsers as well.
Nudge the cache in Chrome following these steps:
Open the developer tools (F12).
Go to the settings (Cog icon).
Ensure that "Disable cache (while DevTools is open)" is checked.
Refresh the page, and the cache will be invalidated.
Right-click the "reload" button next to your address bar and choose "Empty cache and hard reload".
All caches and cookies have now been cleared from your Google Chrome browser. Generally, it is a good thing to do occasionally.
NuGet installs the latest version of the package when you use the dotnet add package
command unless you specify a package version:
dotnet add package Umbraco.Cms --version <VERSION>
Add a package reference to your project by executing the dotnet add package Umbraco.Cms
command in the directory that contains your project file.
Run dotnet restore
to install the package.
For Umbraco 9 If you are using SQL CE in your project, you need to run dotnet add package Umbraco.Cms.SqlCe --version <VERSION>
before the dotnet restore
command. From Umbraco 10, SQL CE has been replaced with SQLite, so a dotnet restore
should be sufficient. If this is not working, then you need to run dotnet add package Umbraco.Cms.Persistence.Sqlite --version <VERSION>
, and then dotnet restore
.
When the command completes, open the .csproj
file to make sure the package reference was updated:
<ItemGroup>
<PackageReference Include="Umbraco.Cms" Version="x.x.x" />
</ItemGroup>
Run an unattended upgrade
When upgrading your Umbraco project, it is possible to enable the upgrade to run unattended. This means that you will not need to run through the installation wizard when upgrading.
Below you will find the steps you need to take in order to upgrade your project unattended.
Enable the unattended upgrade featureAdd the Umbraco:Cms:Unattended:UpgradeUnattended
configuration key.
Set the value of the key to true
.
{
"Umbraco": {
"CMS": {
"Unattended": {
"UpgradeUnattended": true
}
}
}
}
With the correct configuration applied, the project will be upgraded on the next boot.
The Runtime level uses Run
instead of Upgrade
to allow the website to continue to boot up directly after the migration is run. This happens instead of initiating the otherwise required restart.
The upgrade is run after Composers but before Components, and the UmbracoApplicationStartingNotification
. This is because the migration requires services that are registered in Composers, and Components require that Umbraco and the database are ready.
Follow the steps outlined below to use unattended upgrades in a load-balanced setup.
Deploy to all environments.
Set the Umbraco:CMS:Unattended:UpgradeUnattended
configuration key to true
for the Main server only.
Boot the Main server, and the upgrade will run automatically.
Wait for the upgrade to complete.
Boot the Read-Only servers and ensure they do not show the “upgrade required” screen.
The steps outlined in this article apply to Umbraco version 10 and later versions.
Are you upgrading to a minor version for Umbraco 6, 7, or 8? You can find the appropriate guide below:
Minor upgrades for Umbraco 8 Minor upgrades for Umbraco 7RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4