In my experience, the current collision checks are indeed very restrictive.
I am admittedly way out of my depth on this, but I believe the collision checks work by simply checking if the URL resolves to a node, so is it possible you could use route hijacking to first stop the path you want to use from resolving to anything, then let it do the collision check, and then wire the URL back up the way you want it with a UrlProvider/ContentFinder?
Implement the "ultimate" site structure
I would like to implement the "ultimate" site structure found at:
https://24days.in/umbraco-cms/2014/urlprovider-and-contentfinder/
https://cultiv.nl/blog/tip-of-the-week-the-ultimate-site-structure-setup/
However, it doesn't seem to be possible with the current collision checks:
https://github.com/umbraco/Umbraco-CMS/blob/cf86409e3fec4198744189a48255543fc2f32614/src/Umbraco.Web/Routing/UrlProviderExtensions.cs#L70
Anyone have suggestions on how to implement? Or is there a new/better practice?
In my experience, the current collision checks are indeed very restrictive.
I am admittedly way out of my depth on this, but I believe the collision checks work by simply checking if the URL resolves to a node, so is it possible you could use route hijacking to first stop the path you want to use from resolving to anything, then let it do the collision check, and then wire the URL back up the way you want it with a UrlProvider/ContentFinder?
is working on a reply...