Is there an issue related to moving files when using the VirtualPathNativeProvider? When an editor moves a file (cut/paste) in the epi file explorer which is referenced from a page, there will be a warning that this image is referenced. But what happens next is that the reference will be broken. I thought since epi understands that there is a reference, it would automatically update the reference?
I VersionedPathProvider handles this. But I'd like to avoid to go that road just to get this functionality if possible, since it adds a layer of complexity and performance overhead that's not wanted. Or does everybody else use the VersionedPathProvider?
I assume it would be possible to subscribe to the relevant events and do the reference update thingie ourselves but we'd like to use as much OOTB functionality as possible.
Is there an issue related to moving files when using the VirtualPathNativeProvider? When an editor moves a file (cut/paste) in the epi file explorer which is referenced from a page, there will be a warning that this image is referenced. But what happens next is that the reference will be broken. I thought since epi understands that there is a reference, it would automatically update the reference?
I VersionedPathProvider handles this. But I'd like to avoid to go that road just to get this functionality if possible, since it adds a layer of complexity and performance overhead that's not wanted. Or does everybody else use the VersionedPathProvider?
I assume it would be possible to subscribe to the relevant events and do the reference update thingie ourselves but we'd like to use as much OOTB functionality as possible.