Hello, I have a question about configuring Jahia to use a shared drive as it's WEB-DAV document repository. The objective is to continue to reap the benefits of Jahia's "through the web" file linking (e.g. when adding a file to a file portlet). I do not at this point want to use Slide as the store for our working documents. A fair number of users have mapped drives, and our observations about Slide's performance and concurrency issues have steered us away, at least in the short term, from reconfiguring those user's shared drives to point to Slide.
Secondly, is there a way to configure Jahia to "rewrite" the links that Jahia creates such that when a user clicks on a link in a File portlet, they are directed to the file through their mapped drive so that subsequent save operations end up putting the changes back to the correct location? The purpose for all of this is to allow beginning Jahia content editors to make links to existing files through the Jahia interface without having to insert the UNC path or the mapped drive path prefix when creating the link. Regards, -tyson
