Originally added to note Fri, 23 Dec 2011 - 10:50. Now separated.
I like a clean house. At least where a web site is concerned. That means that
- in the file system, images should be organised according to, for example, product images, profile images, images on profiles, utility images, slideshow images, other images (for example). In all cases, I do not like all of these bunched up together in the files directory. Plus image cache will add its own directories anyway. All these need to be accessible by authorised (admin) users.
- all uploaded images should be easily reusable to show in any content type. There should be no need to re-upload existing images again.
- for the user system, all images should enter a photo album that collects all uploaded images. Access could be set to permit users access to either their images only or more or all images. This means that all images can be easily reused anywhere, without needing to upload them again. The photo album could show (to users with permission) exactly where images are being used on the site.
Ubercart would work the same way, an image could be uploaded and enters the product node and the photo album.
- at the same time, we'd have a functional, nice photo album! Parts may be chosen to be internal (admin) other parts public.
Hm, I don't have a good photo album yet...
- deleting an image should delete an image from the server, including all imagecache versions, if there are no other instances of the image showing on site anywhere else, regardless of the user name who deleted it. When a final instance is deleted, the image and all associated remnants of it are deleted.
So far, following forward looking methods, I have not found a way to do these (relatively natural sounding) things, while some forum posts confirm these questions as currently not (easily) solved. At least not for me.