Closed (fixed)
Project:
Image
Version:
6.x-1.x-dev
Component:
image.module
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
12 Jun 2005 at 22:22 UTC
Updated:
11 Aug 2009 at 16:44 UTC
Jump to comment: Most recent file
Comments
Comment #1
zach harkey commented-1
I am opposed to yet another "feature" request for the image module.
Uploading one file at a time is simply not "VERY" tedious. Plus, it's much better from a simplicity standpoint if there aren't a bunch of extravagant features bloating the image module. Things like uploading more than one file at a time, square thumbnails, the ability to choose the order of thumbnails, navigate to the previous and next image in a gallery, or produce valid xhtml, are just not something that most people would use or even care about. To be honest, I'm not sure we really even need to upload one image at a time.
See, I'm hoping that as time goes on, even the ability to upload images will be replaced by a simpler, somewhat cryptic, system of theme_callbacks that will redirect image links through a template layer and on to a separate FTP directory where you can easily place your images by launching an FTP client, logging in, switching to binary mode and uploading the files.
It should all work flawlessly thanks to a matrix of administrative settings through which you will only have to enter several non-web accessible 'file system' paths, which will work hand in hand with the other 'web accessible' addresses, which will all be kept in check by a series of chmod 777'd tmp and temp directories and apache owned sub folders which will contain another folder where all of the images you and your users upload from here to eternity will exist - at one level.
Not only that, but providing you remembered to create and prepare a gallery in advance, you will now be able to open up your image node and attach it to a taxonomy that will serve as a gallery. You won't even have to administer your galleries or worry about which thumbnail represents the gallery because that will all be decided automatically through an intuitive and self-explanatory uri path like taxonomy/term/tid/view/vid/image/133+9,7.
If, after all of that, you still absolutely must have some obscure feature, it's as simple as writing your own custom module and whallah!
Of course you can always pray for a miracle ;)
Comment #2
dreed47 commentedAre you really suggesting to rely on end users to use an FTP client to upload images? I don't know about your users but that won't fly with my users. And if you don't believe it's tedious try uploading 20 images into a gallary......one.... at.... a.... .time.
I also don't believe that this is some kind of "obscure" feature. I'm not the only one asking for this in Drupal. Most image gallary solutions out there provide this kind of functionality (and not via an FTP client).
Ok, if there is no hope of image.module adding this then guess I'll take a wack at writing my own "custom" module for this "obscure" feature.
Comment #3
ezheidtmann commentedI believe zachharkey was joking. He did reference this module, which looks like it's exactly what you want:
http://drupal.org/node/23645
Comment #4
TDobes commentedThere's a patch pending for this, but it simply goes against the design mentality of the image module. The module was designed to have the bare minimum needed functionality and allow users to add other modules for exactly the functionality they want/need. That's why there's a image_import module. You should try it and see whether it fits your needs.
Comment #5
dreed47 commentedJust thought I'd post a follow-up note for anyone interested in what direction I went with this.
I looked at the Image publishing module by Sam Revitch. Really cool! This really IS the ideal way of managing large gallery (or multiple galleries) of images. I will use this to manage image galleries of some of my sites. I'm still not convinced that this fits the bill for my project that prompted this email. My users are not likely to what to run a separate client application to manage images. This site has to pass the "Mom" test, that is, would MY Mother be able to figure out how to use it? I'm still trying to get the Java applet version of the remote client to work within Drupal. I'm not a big fan of Java applets as you can run into JVM compatibility issues. If there was/is a simplified applet version of a remote client that didn't require any setup for the image repositories and didn't require the users to sign-in again this still may be a candidate for my current project.
As for image_import.module. I've used it before and it also works great. I think it's a great tool to load dozens or even hundreds of images at a time. BUT, doesn't pass the "Mom" test :-(. Importing images is a two step process requiring the user to somehow get the images to a directory on the server first.
What I really wanted was the album.module but with support for taxonomies. This would allow me to use the image gallery views that come with the image.module. Soooo. That's what I did. I took the album module and hacked it up for my purposes. It really didn't take much. I just added in the code to display the image taxonomies for the user to select while uploading and then added the call to the taxonomy_node_save() function to save them once the images are uploaded. In my version (image_upload.module) I also removed the support for the folksonomy based "albums" and I added a admin setting for the number of uploads permitted at one time. I'm not really sure where the Drupal group is going with the use of folksonomy and taxonomies. But for my limited purposes it was just easier to pull out the folksonomy-based album stuff and use the taxonomies.
Anyways, it seems to work great AND I think it passes the "Mom" test.
This is the way that I look at these different image upload solutions.
Image Publish module - Ideal tool for site admins or experienced site users for managing large image repositories
image_import module - the best tool for loading a large number of images at one time into your Drupal instance
my image_upload module - Ideal solution for novice end users wanting to save a few mouse clicks and load 10 to 15 images at one time.
Any ways....just my 2 cents
Comment #6
dreed47 commentedI forgot to upload my image_upload.module code in case it's of interest to anyone.
Here it is.
Comment #7
Emiliano commenteddreed47,
Good job! :-)
You did exactly what I needed and it worked fine!
Thanks a lot!
Cheers,
Emiliano.
Comment #8
dreed47 commentedComment #9
chrislabeard commentedsubscribe