Image FUpload: Multiple Images to 1 node

This was already planned but it is not as easy to realize as it sounds. Especially, if you want add or remove images from (to) a already existing node.

I would really like to hear some possible methods.

I can imagine that this is problematic, especially considering the difference in image handling between imagefield and image (file based vs. node based). May I ask what route you chose to go? Maybe it could be handled by some kind of referencing or image_attach, to keep the node-based image handling in the background?

To bring you up-to-date, my plans which are partially worked out:

At the moment, I concencrate on working out the UI of ImageField with FUpload support. By using CCK ImageField's administration form, you can choose whether 1 or 2-unlimited (or restricted value) images should be possible to upload via Image FUpload.
If you chose to be able to upload more than 1 images and edit any image node, the normal ImageField list (of images) will be shown, so it's possible to remove some images. Additionally, below this field, Image FUpload will be integrated to be able to upload some more images to that "node gallery" (--> file based). All right? ^^
On the other side, the image module only supports the node based solution and this won't change next time.

@ scroogie:
The imagefield thing (node based) can easily be done by using taxonomy or node_refernce (for grouping options), this should not be the problem. Or was it another question?

Well, I meant something different. My idea was instead of using the imagefield mechanism (files table) to provide a CCK widget which creates the image node on the fly on submit (if this is even possible?). This would maintain the same images for both the image.module and imagefield.module, when used at the same time. I guess with your version you have got two completely seperate set of pictures, ones for imagefield.module, and the others for image.module, right?

I think I might be explaining it badly, because apparently you misunderstood as well Miraploy. What do you mean with duplicate images?
It is the problem I see with grandcat's solution, that image and imagefield upload images are not interoperable.

Yes, that's right, but I don't think that's a good idea to sync image and imagefield modules because in most of the cases, only once is activated (or installed). If both, this would exceed the task of this project, another module which does it, would be better.

P.S.: IN D7, this should become possible more easily because of some image related hooks =)

Another solution would be to provide an own CCK field for imagebrowser, which doesn't use imagefield at all. Why would you need imagefield anyway? It would certainly be nice to be able to have a CCK field for images, even when image.module is used, especially being able to add already uploaded images to nodes.

subscribe

ImageField is very popular and makes it more easy to interact with CCK core. It would also exceed the project to provide a full CCK implementation. Arguments against are welcome ;)

subscribe

We only need one issue for CCK implementation:
http://drupal.org/node/322473