We are experiencing a bug that was resolved in EPiServer.CMS.Core 10.0.1 in our EPi application running EPiServer.CMS 12.15.1.It seems to be connected to the database in some way. If we use a clean database setup from scratch we don't experience this issue.Does anyone have any clue how this can happend based on the content in the database?Link to the old resolved issue:https://world.optimizely.com/documentation/Release-Notes/ReleaseNote/?releaseNoteId=CMS-1320
Hi Paul,The DB you're having issues on, did that start as CMS12 or was that upgraded from a CMS11 DB? Do you have multile languages available for your pages?I've seen an odd handful of issues in upgraded databases, but it was usually small scale and I could just recreate the content to resolve it.
What does your logs say?
Hi,We resolved the issue ourselves.We had the action for our error-page inside epis EPiServer.Web.Mvc.PageController<T> which made EPI think it was as internal url in epi and not a generic error page path.We moved the logic into its own controller and the problem no longer appeared.