BoldMinded acquires Ansel, support ending for all add-ons. Read More


Support has been discontinued. Issues remain available as an archive.

Could Ansel use the native File Upload conflict handling?

#6 opened by Matt V

Description

I've noticed that if you drag an image to an Ansel field that already exists on the server, Ansel will upload it anyways and rename it with a hash: existing-image-58d032ec7ce8a.jpg.

I know that this is a design choice, not a bug. And I can appreciate that it is slicker to not interrupt the uploading of multiple images for a name conflict. But I worry that my content editors are going to start cluttering up the image source directory with a ton of identical images, which will be: wasteful of hosting space, confusing when browsing the directory for an existing image, and difficult to clean up if three versions of the same image are used in three different entries.

Would it be possible to adopt the native File Upload conflict handling (or something similar)? EE now allows you to select from:

  1. Append numeral to newer file: existing-image-1.jpg
  2. Rename newer file new-image.jpg
  3. Replace older file with the newer file

I guess there's an implicit fourth option as well: Cancel Upload.

Again, I understand how this could make the interface less slick. But it seems to me that it would be helpful to alert the user that the image might already exist on the server rather than silently cluttering the file directory in the background.

Replies

  • TJ Draper

    Replied 3/20/2017 4:11 PM, Edited 11/10/2018 10:09 AM

    As you suspected, I'm not keen on implementing this because I have always found users hate being interrupted with conflict resolution options or even just having to make a choice.

    From a technical standpoint, I'd have to refactor a few things because conflict resolution does not happen until post as it stands right now.

    I'd also have to implement some sort of UI for displaying conflicts and presenting options that is still congruous with the drag and drop upload experience. It's a little easier for EE to do this because it's already a modal, one at a time experience.

    This is not to say I would never implement something. I'll keep it in mind. But I don't expect to implement this soon if I do implement it.

  • Matt V

    Replied 3/20/2017 8:50 PM, Edited 11/10/2018 10:09 AM

    Thanks for the reply, TJ. That's kind of what I thought your take would be. And as I said, I understand the choice.