AnsweredAssumed Answered

Versions not handled by the contentStore selector ?

Question asked by jservajean on Oct 20, 2014
Latest reply on Oct 31, 2014 by jservajean
Hi all,

I have set a new store in order to stream some selected content to a specfic hard drive, by means of the contentStoreSelector.
Using the "cm:storeSelector" aspect and "cm:storeName" works really fine for the main document (content is moved to the new drive), but all the older versions of the document (cm:versionnable) remains in the older content store.

Is there a way (by configuration/tweaking) to have the versions moved along with the current version during the operation ?