Page 1 of 1
File manager - replace files?
Posted: Tue Feb 11, 2014 9:21 am
by rbaby
Any time I upload a file via file manager, instead of replacing the existing file, it will append (#). Is there a setting I can get it to just replace the file of the same name, as opposed to doing this?
Thanks!
Re: File manager - replace files?
Posted: Tue Feb 11, 2014 9:54 am
by Rolf
I noticed this too. In latest release we updated the modules upload software. Looks like this is a "feature" of it...
Re: File manager - replace files?
Posted: Tue Feb 11, 2014 11:49 pm
by paulbaker

Ouch, yes just checked on a 1.11.10 site, you're right.
Ideal behaviour, I suppose, would be a check for same filename and a "Do you want to overwrite file y/n" dialog.
Re: File manager - replace files?
Posted: Wed Feb 12, 2014 12:00 am
by rbaby
Guess there is no setting then, is this something that we can request to amend? As it stands, I can't update files I have to delete it and then re-name the filename (1).ext and that's not ideal on high-impact files such as js files.
Re: File manager - replace files?
Posted: Wed May 21, 2014 4:23 am
by rbaby
Rolf wrote:I noticed this too. In latest release we updated the modules upload software. Looks like this is a "feature" of it...
Thanks, is there any plan of making it so you can replace...? This is an issue even on images that need to get replaced.
Re: File manager - replace files?
Posted: Thu May 22, 2014 12:51 am
by paulbaker
Hoorah.

This appears to have been resolved in CMSMS 2.0 which is currently in
Beta test.
When you upload a file of the same name it silently overwrites the original file. This is much more intuitive behaviour.
Re: File manager - replace files?
Posted: Tue May 27, 2014 1:21 pm
by Guido
Great, I also believe this is the best choice.
99 out of a 100 times it's the admin who uses the file manager, who knows what he's doing so probably won't upload a wrong file. It's annoying to delete the old file every time before you can upload a new one.
Re: File manager - replace files?
Posted: Mon Jun 23, 2014 3:51 pm
by cmsgenie
Unfortunately this is causing a problem right now for my users on 1.11.10. We may be some way from a CMS 2 release, and so 1.11.10 is the current production version.
Is there anyway this change can be ported into an updated FileManager for 1.11.10?