I don't like having to see paths like "files/imagecache/thumbnail/thisoneimagetype/image.ext" instead of "files/images/thisoneimagetype/thumbnails/image.ext" and would love to have the option to customize the path in even the smallest way. Why not allow the "imagecache" path to be "images", like the Image module?

See, my problem is that the main image is in "files/images" while the imagecache-generated images (all the scaled-down versions) are in the imagecache directory. I would simply like to merge the directories and have one seemless directory of images. If it's a problem with the Image module, I'll disable that module. I don't care for that module, anyway! (Why do you think I switched to imagecache? Image module doesn't have nearly enough control.)

Anyway, I think the simplest solution is to allow a custom base path to replace "imagecache" with whatever you like. Instead of "files/imagecache", I'd be able to simply use the same "files/images" directory.

Comments

daemon’s picture

daemon commented

I second that request, it becomes important when Google Images start indexing your pictures!

TapSkill’s picture

TapSkill commented
Priority: Minor » Normal

I'm bringing this issue back up.
As far as I know, a solution has not been presented.

TapSkill’s picture

TapSkill commented
Status: Closed (works as designed) » Active
mrtoner’s picture

mrtoner commented
Status: Active » Closed (works as designed)

I'm going to close this out for drewish. 'imagecache' is a part of the path because the module uses that for the menu callback. Allowing the user to change this is a support nightmare, with the potential for collisions with the menu callbacks used by other modules.