Upgraded umbraco 13 to umbraco 17. Installed Umbraco.Cms.DevelopmentMode.Backoffice so the site starts loading the content.
Only the homepage is loading. All other nodes link simply shows:
“This document is published but its URL cannot be routed”.
I checked culture and hostnames. They look fine. I have 2 domains in culture and hostname:
localhost:44370 English(united states) webseamsters.com English (united states)
The homepage shows both and loads with localhost:44370.
All other nodes show:
“This document is published but its URL cannot be routed”.
and webseamsters.com English (united states)
Why the localhost:44370 is not shown and “This document is published but its URL cannot be routed”. shows instead? and why the other domain name shows without any path? just the absolute domain name.
This is same for every node/nested node I open and no pages load except homepage.
which has the following response for “/umbraco/management/api/v1/document/urls“:
"urlInfos": [
{
"message": "This document is published but its URL would collide with content 4babb907-cc10-4456-bc45-d12cf9a754aa",
"provider": "umbDocumentUrlProvider",
"culture": "en-NZ",
"url": null
}
]
I resolved this by republishing all the nodes. Approach I took was to use Codex / Github Copilot AI agent and telling it to migrate site from Umbraco13 to Umbraco17. Once this was done, the site got migrated, but the inks had issued. Asked codex to republish all the nodes after sharing the error code with it. That fixed the issue.
you can tell codex to fix this “This document is published but its URL would collide with content 4babb907-cc10-4456-bc45-d12cf9a754aa”
and hope it fixes. Make sure to use Umbraco MCP with Codex or Github Copilot agents. Agent alone will not be able to fix.
You sir are a gent and a scholar!
I’m builder (auditioning) my first Umbraco site on v16 and have a meeting with the board to demo in the morning and this exact thing just happened to me. Your solution worked like a champ!!! Thank you
Encountering the same issue now on a site with many hundreds of nodes. Republishing them all by hand is not feasible, calling publish from an upper node does not seem to republish its descendants (despite a message telling me it will).
I guess the only remaining course of action here is to republish all the nodes via a custom API or something?