Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
Your solution creates image (nodes). Imagefield support would (presumably) use the same solution to allow multiple cck nodes with imagefield attachments to be creating (similar to imagefield multiple upload) in a "drag and drop" manner...
I'd like to work on this so I'm re-opening it. The solution would still be a single imagefield per node, but using imagex to upload them and create the nodes.
Keeping my eye on this. I know several users who would find this incredibly useful. I'm no programmer (still) but will be happy to put it to the test. I'm committed to imagefields for now.
If image.module would just make the jump to using FileField, then other modules, such as this one, would know which direction to go in.
ImageField Assist has already forked Image Assist, and they define a node type using content_copy.module, so you could probably go ahead and use that as a de-facto standard.
Comments
Comment #1
sdrycroft commentedIf you can explain how it would work, then perhaps, but unlikely.
Comment #2
1kenthomas commentedYour solution creates image (nodes). Imagefield support would (presumably) use the same solution to allow multiple cck nodes with imagefield attachments to be creating (similar to imagefield multiple upload) in a "drag and drop" manner...
Comment #3
plasticlax commentedor better yet, optionally upload multiple images to a single multi-imagefield, rather than creating a node for each image.
Comment #4
gregglesI'd like to work on this so I'm re-opening it. The solution would still be a single imagefield per node, but using imagex to upload them and create the nodes.
Comment #5
messenger commentedKeeping my eye on this. I know several users who would find this incredibly useful. I'm no programmer (still) but will be happy to put it to the test. I'm committed to imagefields for now.
Comment #6
Scott J commentedIf image.module would just make the jump to using FileField, then other modules, such as this one, would know which direction to go in.
ImageField Assist has already forked Image Assist, and they define a node type using content_copy.module, so you could probably go ahead and use that as a de-facto standard.
Comment #7
gregglesAnd here's a patch for it.
There are a couple of things I could do differently, but the code works for both modes.
I introduced a settings page to handle choosing whether to use Image or Imagefield and, if Imagefield, which content type/field to use.
The theory is that it works with a setup where you want 1 imagefield per node.
Comment #8
gregglesFor e_all compliance we should add
To the top of imagex_requirements.
Comment #9
Anonymous (not verified) commentedHas this been rolled into the latest releases? This seems like it could be really helpful in my use case.