Hi Isaac, Yeah, that's not a bad solution but what do you do if the client wants to dump a category? You still have an unwieldy single directory of files to pour through. Plus I've found it's not hard to give the client a naming convention to follow.
Nick Isaac Reuben wrote: > The way I've done it before is to name the images according to the item > number, like so: (for item #312) > > p312s.jpg (small thumbnail) > p312m.jpg (normal) > p312l.jpg (large image that opens in a pop-up) > > (the "p" is for "product" -- there are other types of images in there too, > like "c" categories and "b" banners) > > This naming happens automatically when the image is uploaded, so it doesn't > matter what the file was named on the client side -- there can't be mistakes > in naming. When a user goes to view the item page, the code checks if there > is an image file with that products id, and shows it if there is. > > This makes for a giant directory of somewhat obscurely named images, but you > should never have to even look at the filenames because it's all managed > through the web interface. If you are adding large numbers (100's) of > images at once, you can run them through a script (to resize them to the > three sizes, for instance) and generate the appropriate names automatically > (starting with a file like "312.tiff") and then don't have to do it all > through the web for each item. ---------------------- Lab2 Design-Unit URL: http://www.lab2.com.au e-mail: [EMAIL PROTECTED] ---------------------- _______________________________________________ FreeTrade-dev mailing list [EMAIL PROTECTED] http://share.whichever.com/mailman/listinfo/freetrade-dev
