Try our conversational search powered by Generative AI!
AI OnAI Off
Episerver Draft Preview 404 (CMS version 11.4.0)
Hi Scott, can you clarify your CMS and Commerce version.
I just quickly tested with one site using EPiServer.CMS 11.9.0, EPiServer.Find 13.0.1, TinyMCE 2.4.0. I edited an existing news page (all properties view) and then switched to preview and the page loaded just fine. This site has no custom routing.
Jul 24, 2018 10:53
And to clarify the editor view is working fine with draft pages, it's specifically clicking the preview button in the top menu
Jul 24, 2018 11:01
Aah sorry, my brain refused to read anything after 404 in the title (too many fours and zeros after that ;P).
And just to clarify, I used the preview button in top menu and preview worked.
Jul 24, 2018 11:06
No worries, I should probably add it in the description as well, ironic as I've just blogged on how to write forum posts lol. It's an odd one, but I can't see anything routing wise that would be causing the issue.
Jul 24, 2018 11:12
Don't they say "Do as I say, not as I do."? 
I had an older MVC Alloy site which I updated to EPiServer.CMS package 11.4.0 and the preview works there. So maybe something in your code or an add-on you might be using?
Jul 24, 2018 12:00
Lol yes exactly. Hmmn that's odd, I'll have to think about a way forward to try and identify what's going on. Thanks for the help, I might try disabling all the routing modules for now when I get a chance.
Jul 24, 2018 12:20
We have just noticed that when making a change to a page (creating a draft version) and then trying to preview it we are getting a
HTTP Error 404.0 - Not Found
The underling URL it's generating is /EPiServer/CMS/Content/,,15_2672 which is obviously the content item's reference ID as well as the version after the underscore. Everything is a non draft state works but draft previews aren't working.
We have commerce installed and we do have some custom routes but nothing that should interfere with Episerver's routing. Anyone have any idea if this is an issues that's been fixed or something not known about/a problem in our custom code?