Changing a property on multi language causes "This document is published but its url cannot be routed"

[AreYouSureYouKen]

Using the currently newest version of Umbraco (Version 8.3.0)

We are developing a new multi language website, currently dutch and english and have the hostname domains set up as

websitename.com.local for the Dutch variant
websitename.com.local/en for the English variant

Whenever we change a document type, e.g. add/edit/remove a property, the domain on which we initiated the change, starts throwing the "This document is published but its url cannot be routed" error for pages on the website. It looks like it's mostly pages that are affected by the change made to a document type/element type but sometimes other pages seem to be affected as well.

Deleting the Temp folder in App_Data and giving the IIS AppPool a recycle seems to fix the problem, however, this is definitely not something I feel comfortable putting into a live environment.

Edit: Deleting the Temp folder doesn't seem to be necessary, recycling the app pool looks to be enough.

[kjac]

Hi @AreYouSureYouKen,

I'm trying to reproduce this on 8.4 (RC) and I can't really seem to. Here's what I've been testing:

As you can see, the setup is much like the one you're describing.

When you say the site starts throwing errors, how exactly does this manifest? Is it in the backoffice or the frontend (or both)?

[AreYouSureYouKen]

Hello @kjac

I made a video as well showing how this looks on my end, for some reason it's affecting other pages. When I edit page A it goes well and the error doesn't pop up. But when I edit page B it goes wrong on page A. See gif below:

[kjac]

@AreYouSureYouKen thanks! I'll give it another spin 👍

[kjac]

Hmm no. Still can't repro on 8.4 (RC) despite trying with multiple doctypes and compositions.

[nul800sebastiaan]

Thanks for the tests and helpful gifs @kjac and @AreYouSureYouKen!

@AreYouSureYouKen I would encourage you to take a backup of your site + DB and upgrade that to 8.4-rc and see if you can still make it fail. It looks like it doesn't fail on a clean 8.4 install, so I'll close this for now and assume it is either fixed or it has something to do with custom code you might have.

Feel free to update this issue with new info, we can always re-open it if it's reproducible.

[shearer3000]

hi @AreYouSureYouKen - did you ever resolve this issue? thanks

[AreYouSureYouKen]

Hello @shearer3000 unfortunately not no. It is still something that can happen when we change a document type or add a new one. Recycling still fixes this problem but it's not something you want to be doing on a live-server.

[hfloyd]

I came across a more insidious version of this issue while working on a v7.15.4 -> 8.6 migration.

This site doesn't have any multi-lingual variants, but every single node was showing "This document is published but its url cannot be routed" in lieu of the URL link.

Deleting the App_Data/TEMP files, restarting, recycling the AppPool, even writing a webapi to loop through and re-save every content node in the site had no effect on the issue.

Finally, I tracked down the problem to custom code migrated from AppStarting/AppStarted events. When I commented out that code, rebuilt, and refreshed the back-office - now all the links have appeared.

[vladicaivanovski]

8.9.1 still happening. I can't create nodes because of this error: This document is published but its url cannot be routed.

My app is hosted in Azure as App Service. I tried both Memory Cache - Reload and Database Cache - Rebuild, none of them helped.

Any plan for resolving this issue?

[sveinnmar]

Hi @vladicaivanovski

8.9.1 still happening. I can't create nodes because of this error: This document is published but its url cannot be routed.

My app is hosted in Azure as App Service. I tried both Memory Cache - Reload and Database Cache - Rebuild, none of them helped.

Any plan for resolving this issue?

Did you resolve this? I am experiencing this currently and done everything you mentioned, but nothing seems to fix it. Hasn't happened on LIVE yet but is happening on STAGING for some reason. Worried this will start happening on LIVE.