6

Your assumption is correct. The preview token is only set after Update Preview is clicked. It's always been this way. Not this cookie no. It's set by the XPM client when it retrieves a result back from the Update Preview call Not that I am aware of. Note that Session Preview != XPM. It's a subset feature of XPM, so the IsSessionPreview property is behaving ...


2

What you describe in your last comment is the normal behavior when the Session Preview is turned off or is not working properly. I have witnessed the exact same flow when I'd manually turned off Session Preview (as part of an earlier investigation on a project). So... as Rick mentioned, check your Session (Preview) setup. This includes the required ...


1

There is a moment between requesting a new page and having it rendered where it actually does not exist (i.e. a legitimate 404). However, Experience Manager can handle this moment through a configured "blank" page, delivered through the root folder of your Staging site. See the Documentation for instructions for creating a blank se_blank.html to avoid such ...


1

I have seen similar issues, it’s because of XPM markup tag ComponentTemplateID is empty on that page some of the components, that is why it’s throwing the Invalid URI error while Finishing Editing in XPM inline while updating the preview button. You can check these values in view source of the page to see those markup page, you can also see in the chrome ...


1

So I went with sending current components used as XPM prototypes through a small WF to get them to Draft. When New Page is used in XPM this status is copied into the new component, preventing it from begin published (via minimum approval status) when initial created.


Only top voted, non community-wiki answers of a minimum length are eligible