Skip to main content

Timeline for XPM behavior while editing Page

Current License: CC BY-SA 3.0

11 events
when toggle format what by license comment
Jun 12, 2017 at 18:48 comment added GVK Hi @RickPannekoek, we are on Tridion 2013 SP1 HR1
Jun 8, 2017 at 18:00 comment added Rick Pannekoek Which version of SDL Web/Tridion are you using?
Jun 8, 2017 at 2:04 comment added GVK Hi @RickPannekoek, when I clicked Update Preview button, I see an entry in Items table for a minute or two, but the page is not showing the modified content. Any idea why the modified content is not shown on the page?
Jun 7, 2017 at 19:02 comment added GVK @RickPannekoek, where is this "preview-session-token" set?
Jun 6, 2017 at 19:33 comment added Rick Pannekoek The Session DB should get updated when you press the "Update Preview" Button. At that time, XPM will send a GetPreviewToken request to CM, which will render the updated Page and/or DCPs and then sends this "session preview" to CD using the Preview Service. CD stores the session preview in the Session DB and returns the Session ID. Finally, XPM re-requests the Page, but with the Session ID in a preview-session-token cookie.
May 31, 2017 at 19:29 comment added GVK I see only Items table from SessionDB getting updated when "Finish Editing" is clicked and the Page entry vanishes after sometime. I don't see any other table getting updated when the Page is in edit mode or when editing a Component inline. Also, when adding a Component doesn't show the new Component on the Page. Clicking on Update Preview button also doesn't show the new Component added (If I open the Page in CME, new Component Presentation is found). Once I click on "Finish Editing", the changes are published and I am able to see the new Component. Am I missing any configurations?
May 31, 2017 at 16:13 comment added Alvin Reyes And I'm pretty sure adding a Component or changing a Component Template count as a page change, which should start a save and publish action followed by an automatic refresh (and prompt to the user to refresh if they don't want to wait). In that case it's probably best to wait for the reload rather than try updating the preview.
May 31, 2017 at 16:11 comment added Alvin Reyes For #2, just editing a Component doesn't necessarily create a newer version. In the CME the user must save the Component to create a minor version. In XPM, I believe Component changes are at least detected when changing the selection (click outside the Component Presentation).
May 31, 2017 at 8:25 comment added Bart Koopman Might be useful to add that Update Preview is there to render the page again showing you information from your session, in case the view isn't updated accordingly. By default after adding a new Component, or when editing a Component, you will already see your changes, pressing the Update Preview button shouldn't be necessary. But if inserting a new Component places the item in a wierd place, because your Page Template might do a specific ordering in a region for example, you might want to Update the Preview, to have the Template code executed again.
May 31, 2017 at 8:15 history edited Bart Koopman CC BY-SA 3.0
edited body
May 31, 2017 at 8:04 history answered S. Gabriel CC BY-SA 3.0