When we load our pages in XPM the browser console appears to be showing several 404s for resources:


I checked on the CMS server and there's only 6 non-English frame JS files, nothing for en-US.

A call from Editor_v7. seems to be looking for se_blank.html returns 404.

We also have a couple of exceptions:

Uncaught SyntaxError: Unexpected token ILLEGAL 

Uncaught ReferenceError: Invalid left-hand side in assignment

Is our installation just knackered?!?


So the se_blank.html appears to be normal XPM behaviour, but as our application is DD4T we need to handle that route.

1 Answer 1


In my XPM DD4T implementations se_blank.html is hardcoded in the controller to return an empty page with status 200 HTTP code - once thats in place, XPM will work normally again.

The missing culture file is "normal" - we raised a ticket with support and they said this was intentional.

  • Thanks Rogier - so you have the missing culture file?
    – Neil
    Oct 16, 2014 at 9:50
  • Updated my answer - missed that part :) Oct 16, 2014 at 10:01
  • What about when the staging webapp is running under another context root than /? In that case its no use putting se_blank.html in the webapp root, nor publishing it, since the request for se_blank never reaches the webapp. Any solutions for this, apart from an additional webapp running under / containing only se_blank.html?
    – Para Jaco
    Dec 19, 2014 at 18:19
  • I usually use an apache/ngnx proxy to make sure the applications are routed correctly and protect the appserver. Such a proxy server could also host the se_blank.html, or relay into a different context depending on your needs. Jan 12, 2015 at 6:24

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.