Skip to content

Commit

Permalink
Alert people to the drop in support for UmbracoPath configuration in V10
Browse files Browse the repository at this point in the history
If you are upgrading from V7/V8/V9 and have used the UmbracoPath property to rename your /Umbraco backoffice path, then it's super useful to know this isn't possible in V10, and in that context, people might see this is a 'breaking change' - but I understand there may be strict rules about what can be put in the 'breaking changes' section here - and technically the property is 'still there' on the Global settings, the only change is people can't use it for its purpose! - even though it might not be deemed a 'breaking change' - anyway I ask if you would consider listing it here as I do think it will help people prepare for the migration/upgrade to V10 if they can see that this change has been made.

The discussion of the removal is on this issue:
umbraco/Umbraco-CMS#12593
and the change was made in this commit and released in 10.3
umbraco/Umbraco-CMS#13032
(but it didn't work in 10/10.1/10.2 etc it is the razor class library stuff what broke it - so fine to say this is a breaking change in V10 I think)
  • Loading branch information
marcemarc authored Apr 18, 2023
1 parent 8900b6d commit 6805c07
Showing 1 changed file with 4 additions and 0 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -618,6 +618,10 @@ StackQueue has been moved from `Umbraco.Core.Collections` to the `Umbraco.Cms.Co

This setting has been superseded by `DistributedLockingWriteLockDefaultTimeout`.

#### GlobalSetting UmbracoPath cannot be configured

It is no longer possible to rename the /Umbraco folder path by configuration, the property still exists but is hardcoded to /Umbraco and will be removed in V12.

</details>

## Find your upgrade path
Expand Down

0 comments on commit 6805c07

Please sign in to comment.