Some node content pages resulting 404 [10.2.3]

Boris Sokolov

Vote:

We have a bit strange behaviour with some EPiServer commerce node content pages. They are available in Edit mode but on the site we are simply getting 404. EPi Find reindexation doesn't help. We have restarted the site today because of new release. But the issue remains. Furthermore we have one more page having the same problem now.

I don't see anything valuable in the logs.

Tha page itself is quite similar to other ones that are working. So I don't see any issues both from code and from content perspective.

#186179

Dec 13, 2017 15:15

Erik Norberg

Vote:

Have you enabled episerver debug logging and checked how it tries to route the request?

#186186

Dec 13, 2017 15:46

Boris Sokolov

Vote:

Hi Erik,

Url that is loaded looks pretty much ok. Sample page

#186227

Dec 14, 2017 9:38

David Knipe

Vote:

Is the page published, not passed its expiry date? The default behaviour in CMS 10 is to show a 404 if a page has expired

#186233

Edited, Dec 14, 2017 10:44

David Knipe

Vote:

Reference: https://world.episerver.com/documentation/Release-Notes/ReleaseNote/?releaseNoteId=CMS-1320

#186234

Dec 14, 2017 10:46

Boris Sokolov

Vote:

Hi David, The page is published. Furhtermore I was trying to republish it few times and run EPiFind reindexation. The expiry date is in 2027. So no, the page is not expired. <img src="http://prntscr.com/hnc7rx" alt="Expiry date" />

#186236

Dec 14, 2017 11:02

Erik Norberg

Vote:

That the URL is ok wasn't what i doubted, i was wondering if Episerver can resolve that URL to your page.

I don't think Find is involved when resolving an URL, if the URL would have been wrong then it could possibly involve Find.

Enabling log4net debugging will fill your logfiles with loads of additional information including every routing attempt Episerver does when it gets an URL.

#186248

Dec 14, 2017 14:57