There are only "remove" button, but no "replace" field and button...

Comments

quicksketch’s picture

Category: bug » support

That's right, because if you want to replace, you can click remove, then upload a different one. We had way too many buttons that weren't necessary, so I took out the remove button entirely since it wasn't necessary.

catofcheshir’s picture

I think it's nessesary. Replacing image is easier than deleting then adding then re-typing alt/title/description then re-positioning in multiple images list...
"No replace control" can be optional (per field per instance ;) ), or control can be placed differently on form.

p.s. sorry for my english.

quicksketch’s picture

Well at least you don't need to re-position. You can still remove and the re-add in the same place. But you're right you have to retype the alt and title text. Would it be satisfactory if it just remembered the ALT and Title text? Removing the upload field and the replace field significantly simplified the form.

catofcheshir’s picture

Rebembered alt, title and description? Hm.. What if i'm really want to delete this image then add new, different? Field fills these text with rememdered values? I think there are more confusing...

Ok, i can live without replace option, but there must be better solution... Maybe just one button for replace (and appering input fields for replacing)...

quicksketch’s picture

Status: Active » Closed (won't fix)

Here's the original issue #387194: FileField UI Refactoring. I believe the new approach is much cleaner than the previous method and I'd prefer to not make new options. If you can provide a solid design and a patch, I'll consider including it, but left up to me this is something that won't be changed.

corneverbruggen’s picture

Interesting discussion. I agree that the interface is much cleaner now. Big plus! But... but by now I have seen multiple customers/users having trouble with replacing images and loosing alt text + title. I see two scenarios:

1 - Only the image is updated (e.g. an improved product image) and the text should be left untouched, because the image has the same meaning/contents.
2 - The image is removed and replaced by a completely different image: different meaning, so also the alt text + title should be changed.

Until now, i see scenario 1 happening much more often. If that's true for most users, the effort to remove old alt test + title does not outweigh the comfort of not having to copy-and-past the alt text + title to e.g. a text editor and past it back in after uploading the new image.

In addition to that, the (refactored, see #387194: FileField UI Refactoring) filefield module does keep the file description when removing a file and immediately uploading a new one, while still having the clean interface without the replace button and additional file inputs. Wouldn't it be consistent to do it that way too with imagefield?

Makes sense?

alan d.’s picture

Version: 6.x-3.0-beta1 » 6.x-3.x-dev

+1 for this. I am thinking about creating a composite image link field, and losing the additional fields is simply a killer. The helper module "imagefield extended" has opened up the possibility of unlimited additional data with the widget. It will only be a matter of time before others mimic this request.

An image + data is providing a great non-node based data entry without any programming. I'm hoping that bundles in D7 will make this sort of programming redundant :)

Personally I can not find time in the next 3 months to help sadly