<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">2014-02-27 5:33 GMT+01:00 Markus Klein <span dir="ltr"><<a href="mailto:klein.t3@mfc-linz.at" target="_blank">klein.t3@mfc-linz.at</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><br>
2) Uploading existing files<br>
When a file with an existing filename is uploaded and conflict mode isn't set to override, I think the system should check if the content of the old and new file are the same (compare there hashes). When they are the same the system should handle the upload as succesfull (maybe with a different log message in system log then a normal succesfull upload). From the editors pov I think this would be a great improvement. Especially for the DocModule file upload.<br>
<br>
</div></div>Assumption: Content-hashes are only checked within storage<br>
The cases for uploading a file again are:<br>
1.) same name, same content, override -> mask as successful<br></blockquote><div>Don't think this should be changed. So just override the current file</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2.) same name, same content, no override -> error, tell the user the file exists<br></blockquote><div>IMO this one should "mask as successful".</div><div><br></div><div>Use-case: Editor uploads some files directly in the content element. This way he doesn't have to open the element browser to upload/select files to use.</div>
<div>Now he uploads a file he already uploaded some time ago. </div><div>When we break the upload process with a "File already exists message" the editor still has to open the element browser to search and select the existing file.</div>
<div><br></div><div>If we "mask as successful" the editor is happy and nobody gets hurt :)<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
3.) same name, other content, override -> replace the file content and keep references </blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
4.) same name, other content, no override -> rename the uploaded file<br></blockquote><div>Think this should be the default behaviour again like in the 4.* branches. Not the cancel upload as it now is.</div><div> <br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
5.) other name, same content, override -> rename the existing file and keep references<br></blockquote><div>I'm not sure about this. Are we talking only about files in the same folder?<br>Do not think this is wanted behaviour.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
6.) other name, same content, no override -> error, tell user file does already exist<br></blockquote><div>If you search for files with the same content it could be thats there is a file with the same content but on a location that the editor isn't allowed to access.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Furthermore we lack a 'replace' function, to replace an existing file with a completely different (other name, other content) file, but keeping the references.<br>
This is a MUST HAVE IMHO. </blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=""><br>
What's your opinion about this?</div></blockquote><div><br></div><div>There are currently 3 conflict modes</div><div>1. replace</div><div>2. cancel</div><div>3. changeName</div><div><br></div><div>Currently 1 & 2 are in use by the fileupload in BE. But think this should be 1 & 3. </div>
<div> </div><div>gr. Frans </div></div><br></div></div>