All content unpublished - "its URL cannot be routed"

Questions
1

I’ve got a v15 site that I’ve in-place upgraded from v13, in order to test and swap out deprecrated code/replace any custom angular components.

After a few tweaks the build went fine, and the upgrade process completed, but all content is throwing a 404 on the front end.

Same basic issue as mentioned here; the posts claim to published but it states “its URL cannot be routed” and attempting to re-publish gives the warning “The document does not have a URL, possibly due to a naming collision with another document“ (there are no naming colisions). There is nothing in the internal log viewer to indicate anything further.

I’ve cleared the in-memory cache, and the database cache (cmsContentNu) through the back office, as well as deleting NuCache from the TEMP folder in the Umbraco filesystem. None of these steps helped.

At a bit of a loss as to what to try next, anyone got any smart ideas?

2

Hi,

I’ve just been testing an upgrade from v13 → v16.

I hit this issue - but setting a domain on the homepage (localhost was enough) in the cultures and domains then allowed me to publish. Seems like a nasty bug on the upgrade as everything now needs republishing. Will do some more digging then raise an issue in the issue tracker if I can recreate.

HTH though.

Steve

3

I think most of my unpublished issues are actually due to this: