Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I think the answer is no, but I was wondering if this uses the built in Drupal image system at all. If not, is there a way to display images uploaded through the imce module in galleries or can they only be inserted into nodes? This module seems to work quite well, but I'd like to find a way to use it and allow users to view their images and and create galleries of images as well.
Comments
Comment #1
davemybes CreditAttribution: davemybes commentedThis module does not create nodes or galleries. If you need that functionality, then use the image module (http://drupal.org/project/image).
Comment #2
jasonwhat CreditAttribution: jasonwhat commentedI'm changing to feature request then. Not that I'd love to see it use the image module, but I'm concerned about how large quantities of images are managed via this module. I love it, and it seems like the simplest bug free way to add images with some control.
Comment #3
venkat-rk CreditAttribution: venkat-rk commentedI second jasonwhat's request. The only thing preventing me from using IMCE is the lack of the following:
1.) No way to create galleries from uploaded images/based on user
2.) No support for taxonomy and therefore no way to use the brilliant views module
With additional support for CCK's imagecache/imagefield modules (and perhaps mass upload, although there are separate modules), IMCE would smash pretty nearly every other image related module out of sight.
Comment #4
ufku CreditAttribution: ufku commentedMy main purpose of implementing IMCE was to use images without making them nodes. Actually it's a file uploader/browser, not an image module. I think what many people are looking for a real! image module having IMCE-like features. The question is, should we build IMCE-like features on image modules or build image module features on IMCE? or implement the combination as a new module?
Comment #5
jasonwhat CreditAttribution: jasonwhat commentedI don't know the technical aspect, but from a usability point of view I think the ideal would be to have a file (per user or per site) that creates a node of any image in it. So when uploading the user can choose the "Image Gallery" file that would create an image node, or the "personal library" or whatver it would be called. That said, the great thing about your work on IMCE is it "just works" and does what it is supposed to do, so it might be shame to muck that sleek usability up with new features.
Comment #6
profix898 CreditAttribution: profix898 commentedI think the module is very nice as it is now. But it would be nice if one could also browse image nodes created with the image module. At the moment some users (including me) need to use IMCE and img_assist in combination. I use IMCE to upload, manually resize images and to browse my files (images and non-images) to easily insert them into nodes. I use img_assist on the other hand to insert images from the image module. You may ask why I still need the image module: If I have a large image it creates a node with the original size image (or any custom size) and a thumbnail image. I can then use img_assist to insert a small (thumbnail) image into my node which automatically links to the larger image versions. Thats not possible with IMCE. But IMCE is a perfect module if you want to handle (link/embed) non-image files by browsing your folders or if you dont need auto-resize for your images.
Comment #7
Bevan CreditAttribution: Bevan commented-1 I think IMCE's best feature is that it doesn't create nodes for every image you upload.
Comment #8
ethang CreditAttribution: ethang commentedIs anyone familiar with a work-around for this?
Is there a process to create image nodes per each image uploaded through IMCE? Or is it possible to automatically create an image gallery from a user's IMCE directory?
Comment #9
Bevan CreditAttribution: Bevan commentedTry a module called image import. I think it's packaged with image module.
Comment #10
ufku CreditAttribution: ufku commented