Posted by Jan Krummrey on January 23, 2009 at 10:14am
| Project: | Imagefield Import |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | wulff |
| Status: | closed (fixed) |
Issue Summary
Hi,
first of all thanks for the great module. Mass-uploading of images is still a wakness of imagefield.
I was wondering if it were possible to upload many images into one Imagefield and not into many nodes with one image per field. Would that be hard to implement?
Jan
Comments
#1
subscribe
#2
subscribe
#3
subscribe
#4
subscribe
#5
Would be nice :)
#6
Yes, for me it was expected behavior :-)
#7
I have done some changes to this excellent module, maybe someone could use them too so I am sending a patch.
- images are all loaded into one node only, not one image one new node
- thumbnails with link on importing page
- added a checkbox to decide whether you want to delete source files or not
- after the node creation you are redirected to it's edition page
- you can define node title
- node's author is now filled before saving
Thumbnails will not work if absolute import path is defined, relative path required. I didn't tried to use taxonomy and it probably will not work too. Image's titles don't works when importing, you have to define them in the standard way in edit node page.
Hope this helps.
#8
Thanks - this looks like good. I was playing around with the jifupload module, but I think I prefer this :) Gave it a quick test and it works well.
Note - you have a call to dsm(). You should remove that :)
#9
I haven't yet looked this patch over--
But it seems like a good idea from the outset.
The module works as it does currently, because it was essentially ported from the old school image module.
I think we need to allow the user to perhaps choose to do either 'one image per node' or 'Import all of these images into one node'.
Thoughts?
#10
I would agree with that - there should be some sort of configuration option.
#11
This could be a nice feature. Marking as a feature request for the dev version.
#12
nice, is there a patch updated version against latest release? this is a great addition
if someone could add those additions to the latest or has at least a close to the latest version, please post a working patched version of this module (so we can test) or a working patch to the latest dev
#13
The latest development version of the module now has support for importing images to a single node (which is created during the import).
You can either grab it from CVS or download the development release when it becomes available (it should be built automatically within 12 hours).
#14
I tried the batch import feature and got the following,
An error occurred. /batch?id=112&op=do
Fatal error: Call to undefined function image_gd_check_settings() in /xxx/includes/image.inc on line 70
Wait a minute, this might be an issue here -> #295854: WSOD when the image.<toolkit>.inc file for the selected image toolkit is not found.
OK - you can ignore everything above :) I revisited the image toolkit settings page, and that got rid of the above error. I then tested the batch import and it works well for me :) Thanks!
#15
it worked here too,
some notes/feature requests:
1. You could add a simple global "description" or "title" field for all images. We could use then some predefined file tokens offered by other module
2. The upload methodology adds all original images at once and validates the sum of original sizes not one by one. If you are uploading many hi resolution images this can be a problem. We have to increase the maximum upload size maybe in php also, not tested.
3. The new node that is being created loses all default values in forms (cck too). Additionally If default imagefield is defiled and active, default image is being added to every new node as the first image in the list.
4. ----
5. Support for existing nodes that have already imagefield images uploaded (considering #3) with a nid field to add those nodes, validating if selected imagefield is there, if not prompting for a new nid with appropriate imagefield.
6. We could also define special exif data selections (not just the default camera model) for images e.g. lat lon spatial information, so this info can be printed in description also.
7. Images do not get resized as specified in imagefield settings. Instead full image is being uploaded. Of course batch resizing images in an external application (like xnView) before ftp uploading is better! but should be noted.
very nice feature, i use it already with success, but if someone will try it, sould take care of the above notes
#16
Works well, thanks. #15, point 5 is a good one: I'd like to be able to import into existing nodes.
Also, for each image imported I get the following error message:
The import works anyway. This may have to do with my imagefield uploading to a subdirectory of files.
#17
I get a similar message, about files not being able to be copied. Also, if I import a large number of photos, I get a 500 internal server error, but if I refresh the page, it looks like everything gets imported. Not sure what is happening there.
#18
Does image_fupload satisfy this need? It's a great module, and met my needs in this area.
#19
fupload is a cool module but not for mass importing images into multiple nodes. and it uses flash.
#20
sub !
#21
subscribe
#22
I managed to hack the 5.x-1.5 release to import into a single node. Let me know if anyone would be interested in a patch.
#23
#15:
ad 1) So, if these (optional) fields are filled out, they override the per-image title/description fields?
ad 2) Yes, the size limits should be per image. I'll take a look at that.
ad 3) Sounds like a bug.
ad 5) This seems to be outside the scope of this module, but please file it as a separate feature request.
ad 6) Maybe this could be solved by adding generic token support to the module?
ad 7) I'll try to implement this. It makes sense that imported images should be resized according to the settings.
#24
#15 ad 6) For now, I've made it possible to select which EXIF/IPTC fields to use (is in the latest dev. version).
#25
Wulff, I too am looking for point 5 from #15 above i.e. mapping multiple images to existing nodes.
There is already a feature request for it (http://drupal.org/node/538304), but you marked it as a duplicate of this one, which it isn't according to your post above.
#26
I'd forgotten about the old feature request, thanks for pointing that out. I'll reopen that request and split this issue into separate requests to make them easier to track.
#27
ad 1) See #710038: Add token support
ad 2) See #710040: File size validation handles all images as one
ad 3) See #710042: New nodes are created without default values and #710044: Default image is added to new nodes
ad 5) See #538304: Map imported images to existing nodes
ad 6) Is in the latest release. Let me know if your favorite EXIF/IPTC tag is missing.
ad 7) See #710048: Images are not resized on upload
I'm closing this issue so we can continue the discussion in the new sub-issues.