We have implemented XPM with Tridion 2013 SP1 and DXA 1.2 and disabled "Session Preview" as well. Most of the business use cases are functional.
I am running into the following situation. The publisher edits content (at a global level) using a site level publication (site1). Once editing is completed, the publisher does finish editing and the content / page is pushed to our staging website, within the context of the same publication (i.e; everything with site1)
When the publisher is trying to modify another site level publication (site2) inheriting the same content, the XPM interface shows the old content (published) vs. the updated content (in the CM). The publisher can see the updated content only when they try to edit the global component. It is misleading to the publisher, obviously.
Is there some setting that we am missing which would overcome the above scenario? Any thoughts or feedback appreciated.
Based on the responses, the OOTB approach would be to enable Session Preview. I am updating the question with "Update Preview" enabled in the XPM interface as well.
When I click on 'Update Preview', the XPM interface does NOT throw any errors but it does NOT update the preview as well.
I am receiving the ONLY one WARNING for the following ODATA service (regarding storageTransactionId). No errors or warning in the CM server. Should we do configure the service differently when the storage factory is database vs. file-system?
2017-02-14 09:10:23,186 DEBUG AbstractMethodHandler - Original publication ID for write method parameter [non_entity] is 255. 2017-02-14 09:10:23,186 DEBUG AbstractMethodHandler - Session-publication ID for write method parameter [non_entity] is 284. 2017-02-14 09:10:23,201 DEBUG ReadMethodHandler - Session returned a result for method: findBinaryByPrimaryKey. 2017-02-14 09:10:23,201 DEBUG SessionManagerImpl - Activity on session: 84e12bfb-e137-4a18-8b20-4418cd663184, extending session lifetime until: Tue Feb 14 09:11:23 CST 2017. 2017-02-14 09:10:23,201 DEBUG JPAPreviewSessionDAO - Retrieving PreviewSession by sessionId: 84e12bfb-e137-4a18-8b20-4418cd663184 2017-02-14 09:10:23,201 DEBUG SessionServiceImpl - PreviewSession already exists, updating with PreviewSession [sessionId=84e12bfb-e137-4a18-8b20-4418cd663184, expirationDate=Tue Feb 14 09:11:23 CST 2017] 2017-02-14 09:10:23,201 DEBUG JPAPreviewSessionDAO - Updating PreviewSession: PreviewSession [sessionId=84e12bfb-e137-4a18-8b20-4418cd663184, expirationDate=Tue Feb 14 09:11:23 CST 2017] 2017-02-14 09:10:23,201 DEBUG ODataWebserviceHandler - Commiting webService transaction. 2017-02-14 09:10:23,201 INFO StorageManagerFactory - Committing storage transaction: 60742d32-850a-471c-b180-8949269416fc 2017-02-14 09:10:23,201 WARN LocalThreadTransaction - Could not remove the storageTransactionId 60742d32-850a-471c-b180-8949269416fc from the current thread, because there was another storageTransactionId: null 2017-02-14 09:10:23,201 DEBUG LocalThreadTransaction - Received a set on the new method with value: null 2017-02-14 09:10:23,217 DEBUG ODataService - Adding header to response: X-Preview-Session-Token with value: RwFslE4wuKvGI+z3YJLFZLXSphgRxJ0QrA4abtY8XGcP7lUfT80W0F7fi5ND4AVO 2017-02-14 09:10:23,217 DEBUG AmbientRuntime - Ambient Data context initialization. 2017-02-14 09:10:23,217 DEBUG AmbientRuntime - Ambient Data context initialization.