AurorisNet.Umbraco.ApplicationVirtualPathFix
17.8.1.1
See the version list below for details.
dotnet add package AurorisNet.Umbraco.ApplicationVirtualPathFix --version 17.8.1.1
NuGet\Install-Package AurorisNet.Umbraco.ApplicationVirtualPathFix -Version 17.8.1.1
<PackageReference Include="AurorisNet.Umbraco.ApplicationVirtualPathFix" Version="17.8.1.1" />
<PackageVersion Include="AurorisNet.Umbraco.ApplicationVirtualPathFix" Version="17.8.1.1" />
<PackageReference Include="AurorisNet.Umbraco.ApplicationVirtualPathFix" />
paket add AurorisNet.Umbraco.ApplicationVirtualPathFix --version 17.8.1.1
#r "nuget: AurorisNet.Umbraco.ApplicationVirtualPathFix, 17.8.1.1"
#:package AurorisNet.Umbraco.ApplicationVirtualPathFix@17.8.1.1
#addin nuget:?package=AurorisNet.Umbraco.ApplicationVirtualPathFix&version=17.8.1.1
#tool nuget:?package=AurorisNet.Umbraco.ApplicationVirtualPathFix&version=17.8.1.1
Umbraco Application Virtual Path Fix
Backoffice fixes for Umbraco 17 and 18 sites hosted under a subdirectory, such as
/SomeTestPath/umbraco. Sign-in, backoffice assets, media, dashboard requests and
session renewal stay under the site's application path.
What it does
- Sign-in stays inside the path. Login, management API calls, OAuth callbacks, and password-reset and invitation links use the prefix.
- Backoffice assets load. Import maps, scripts, stylesheets and the logo resolve under the path.
- Media is served under the prefix, including media outside
wwwrootor in a provider such as Azure Blob Storage, with ImageSharp crops and resizes. - Sessions restore cleanly. A fresh browser starts sign-in directly, avoiding Umbraco's initial token-refresh errors. This also helps sites at the root.
- A health check reports the status under Settings → Health Check.
Quick start
Add the package to a website running Umbraco 18.0.0 to 18.3.1 or 17.5.0 to 17.8.1. Reference your site's Umbraco major version, so NuGet installs the newest package for it:
<PackageReference Include="AurorisNet.Umbraco.ApplicationVirtualPathFix" Version="18.*" />
On Umbraco 17, use Version="17.*". A site with central package management needs
CentralPackageFloatingVersionsEnabled for a floating version, or an exact version such
as 18.3.1.2. Then set the site's application path in appsettings.json:
{
"Umbraco": {
"CMS": {
"Hosting": {
"ApplicationVirtualPath": "/SomeTestPath"
}
}
}
}
Start the website and open /SomeTestPath/umbraco.
Versions
A package version is the newest Umbraco release it supports, followed by our release count: 18.3.1.2 supports every Umbraco 18 release up to 18.3.1, and 17.8.1.1 supports Umbraco 17.5.0 up to 17.8.1. NuGet's dependency range spans the oldest and newest supported releases. Check the supported versions to see whether your Umbraco release is tested and supported, and upgrade the package when you upgrade Umbraco.
Documentation
Licensed under the MIT license.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Umbraco.Cms.StaticAssets (>= 17.5.0 && <= 18.3.1)
- Umbraco.Cms.Web.Common (>= 17.5.0 && <= 18.3.1)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on AurorisNet.Umbraco.ApplicationVirtualPathFix:
| Package | Downloads |
|---|---|
|
AurorisNet.Umbraco.AppHost
A shared base for Umbraco sites: single sign-on and account policy, application blocks and Interactive Reports, website and application themes, virtual-path hosting, and the workarounds for upstream Umbraco gaps. |
GitHub repositories
This package is not used by any popular GitHub repositories.