In 4.5.2 there was a directory upload feature. To be honest, it kind of sucked, but it did work. I can't find this feature now. Please tell me it isn't gone that would be 4.6 dealbreaker for me.

Am I missing something?

Comments

sepeck’s picture

There is no such feature in the 4.6 image module. Now, someone mentioned somewhere (I think forum post) that they were working on an module to implement that functionality, but I don't recall who it was or what their status is.

-sp
---------
Test site...always start with a test site.
Drupal Best Practices Guide

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

freyquency’s picture

It seems like some modules are being stripped to their core components and additional features once present are being introduced into separate modules. Not bad, but it'll the downloads page a bit more unwieldy. As it is I have to pack a lunch to make it through.

sepeck’s picture

I believe the point is to make modules more descrete and create 'bundles'. Encourage the creation of modules that do something very well. If it is a 'new' type funtionality, then make the 'core' function of that module very basic and create add-on's to that module. This accomplishes a few things.

  • 1. The module is more focused and hopefully the contributor will give thought to the creation of hooks for others to leverage the module.
  • 2. The availability of slimmer modules that add api functionality of their own, will enable other contributors to add to the module their own 'enhancements' focused on their needs without having to re-invent the wheel.
  • 3. The hope is this will reduce the confusing array of modules that have overlapping/duplicate features but no clear path for site admins as to which will continue or be best to use.
  • 4. If a module grows in use and becomes a candidate for core inclusion, then the basic api functionality will be easier to integrate into core and the bundled modules that rely on it will be easier to update.
  • 5. The add on modules will be more capable on their own focused purpose

-sp
---------
Test site...always start with a test site.
Drupal Best Practices Guide

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

mghandi’s picture

Hi,

there is an image_import Modul, which is working with the new image.modul in 4.6. Perhaps it can help you.

http://drupal.org/node/19860 -> You can find the Modul File in the Sandbox auf the Developer

cu, Sven

paranojik’s picture

I've just managed to modify the 4.5.2 version of the image module to upload ZIP file-packed pictures and add them to the galllery, similar to what the dir upload does. I'll try to post the patch in the appropriate topic.

zach harkey’s picture

Ohhh man, that is so sweet. I'll wash your car if you can pull this off for the 4.6 image module. And if you can get it to generate square thumbnails, I'll wax your car ; )

: z

sepeck’s picture

Take a look at what mghandi posted. Here is the link to the files.
http://cvs.drupal.org/viewcvs/drupal/contributions/sandbox/syscrusher/im...

Looks to do exactly what you want. Just add the new image module. Here is a link the the readme
http://cvs.drupal.org/viewcvs/drupal/contributions/sandbox/syscrusher/im...

-sp
---------
Test site...always start with a test site.
Drupal Best Practices Guide

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

paranojik’s picture

As I promised, I finally submitted the patch for the zip upload functionality. It attached here: http://drupal.org/node/7932

geokker’s picture

I installed 4.6 expecting the same or greater functionality than my current 4.4. I couldn't get HTMLArea to work at all, there isn't a 4.6 bookmarks module and image module has been 'rewritten' and doesn't include most of the features. I think most people will want to use Drupal for simple blogging and image galleries. Feature-wise, it has leapt into the past.

However, I can wait for greater functionality in 4.6 and am quite happy to continue with 4.4. I guess I was just a little disappointed.

chx’s picture

That the image module was a hodgepodge of image, gallery and mass upload functionality does not it was the right way to do it. However, there is Gallery2, mass import and image module -- that's the right way to do it. One module, one functionality. While I like tomato soup and tiramisu as well, I do not think anyone would eat some tomato soup with tiramisu dropped into it...

Simple blogging and image galleries -- Drupal is far more and it is used for more.

--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.

freyquency’s picture

most modules aren't ready the same time the core is. There's usually a waiting period before there are all of the features you use on your specific site. I remember last time with the upgrade to 4.5 I hastily upgraded and realized there was no weblink module waiting for me. You should always check into modules, especially the non-flashy ones you might forget about before upgrading...

I like the image module as it is now. Just not having to find the path to imagemagick is a blessing.

dmjossel’s picture

Gallery 2 is great unless you've already been using image.module for years and have several thousand images in it. Not to mention that it's unclear to me how gallery.module can be called "integration". As far as I can see, all it does is produce a block. For a site that is full of images that are nodes in drupal, with various taxonomy terms assigned to them to make them easy to find in a variety of ways-- simply tacking on a box to link to an external photo gallery program is not an ideal solution.

I really hope the mass-import feature for image.module is added to 4.6, either in the module itself or as a separate module; at least two sites I run on Drupal 4.5.2 absolutely depend on it.

However, at some point it does appear as if Drupal's functionality is being balkanized. I don't ever remember seeing so many "helper", "framework" and "API" related modules before the 4.6 release. Modules don't even do anything any more; they just provide hooks for other modules (which in some cases don't exist yet, and might not ever) that might do something, and features that are logically connected in the minds of users and administrators (image display, image uploading) are being bifurcated.

The idea of cleaning up and rewriting the core is great, as long as the functionality eventually makes its way back into the system, which I hope it does, as it usually has in Drupal's past. However, I'm dreading the day where there's one change too many and the whole thing overbalances. Already lots of useful modules have been abandoned, and others have lost more functionality than they've gained over the last few revisions.

Just a few concerns I have as a long-time Drupal user.

sepeck’s picture

Try this out on a test site and let give the author some feedback :)
http://cvs.drupal.org/viewcvs/drupal/contributions/sandbox/syscrusher/im...

You are correct on the helper framework. The problem with not changing is confusion. Two striking examples are the proliferation of file management modules which all did file management differently or permissions modules which often conflicted if installed on the same site.

The goal is to identify the minimum api funtions to provide a framework for operation, then others are able to write additional modules that all leverage that functionality. You can end up with 2-4 developers collaborating on a base level functionality but going their own way for additional functionality. API moudles get more attention and specific features can potentially be better as they are more focused.

I do not use image import nor do I believe that I will do so in the near future. So for my sites the image import function of the old image moudle is 'bloat' so to speak :). Now, I do not have to use it.

See my post above for some more posibilities. There really seems to be a lot of change and refocusing as the result of the Drupal meeting. 4.7 is going to be even more exciting. Especially now that we have Bryght, CivicSpace and others offering services, Drupal is getting more attention then ever. Unfortunatly moudle lags behind the core release. Primarily as a lot of the contributors are working on core :). They'll catch up or others will jump in.

-sp
---------
Test site...always start with a test site.
Drupal Best Practices Guide

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

chx’s picture

there is album module, too. Which shows why functionality must be taken apart: this way you can have more options.

--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.