I am starting an incremental implementation of Experience Manager (XPM). Due to architectural constraints, we will first implement XPM without Session Preview before rolling out web application changes to enable Session Preview partially (for component presentations) and then fully (for page alterations) in later phases.
The problem I am having is that XPM is not publishing content when I click Finish Editing, and worse still, is not publishing newly created pages (resulting in a 404 whenever a new page is created in XPM). I have recreated this behaviour on a dev system which has Session Preview installed, by disabling session preview AND removing the Session Preview webservice endpoint from the Staging publication target Session Preview settings.
I dont see why if Session Preview is disabled, a valid oData webservice endpoint is required on the publication target Session Preview settings, am I missing the point, or perhaps some other configuration setting somewhere?