Where is the best place to save images so that exporting snapshots doesn't throw errors ? If all the images are just added to the sites folder it is very unorganised without subfoders to manage them. Especially as there are 3 images per product.
Announcement
Collapse
No announcement yet.
Best way to manage image files
Collapse
X
-
Make a sub-folder of your Site folder (say Images) and keep them there. You can also make additional sub-folders of Images if you want, in order to separate product, section and thumbnail images.
Snapshots will now work smoothly and will easily be transferrable to another system.Norman - www.drillpine.biz
Edinburgh, U K / Bitez, Turkey
-
I would suggest a folder called "ProductPictures".
In this folder have 3 subfolders called "Zoom", "Normal" and "Thumb". In each of these folders keep a copy of each product which is sized to the settings you use for "Zoom", "Normal" and "Thumb". Like previously mentioned add something to the filename to differentiate them. I would personally recommend adding a suffix not a prefix, in other words "levi-501-jeans_T", "levi-501-jeans_Z" and "levi-501-jeans_N". This way you you can access the images easier and can change the image you wish to locate easily by just changing the folder location.
Run batches on your images which puts them into the correct folders for you.
Failing that dump all the raw images into an "Images" folder within the site1 folder and contact Norman about using his dynamic image sizing tool.
Comment
-
I'm still working on two problematical areas.
1) If you use huge images (say 2400 x 3200 pixels @ 500Kb) then the
processing time can be 5 seconds per image. At the moment this processing
needs to be done on every upload. I'm working on a way to only do this once when the image is first ever used.
2) I've still not found an easy way to stop the original images from being
uploaded. So if you used 1000 x 500Kb original images you'd need 500Mb
spare space on the server!
Neither stop the patch from working but cost time and resources.
If you always used reasonable sized image to start with (say less than 600 x 400) then there probably wouldn't be any issues and the patch may be useful as-is.
More later.Norman - www.drillpine.biz
Edinburgh, U K / Bitez, Turkey
Comment
-
Great -- thanks Norm ... Although the server size of things don't really matter to me as I have unlimited storage and transfer, the processing time for 1000 images may cause problems. I wouldn't like to be an hour into it to have a ftp problem!Simon Williams
Actinic Designer v.8.5.2.0.0.0.HMVA
Comment
-
If you always used reasonable sized image to start with (say less than 600 x 400) then there probably wouldn't be any issues and the patch may be useful as-is.
Comment
-
Originally posted by RuralWebThis is my plan and am building it into a new site as a live test now to see if there are any major problems. I dont see any at the moment and as norm says if the source image file sizes are kept low then it should work as is - I think that the benefits to builders outweighs the image upload problem.Simon Williams
Actinic Designer v.8.5.2.0.0.0.HMVA
Comment
-
Test product loaded if anyone wants to look http://www.allfusedglass.co.uk/acatalog/Jewellery.html this is created from an image taken stright from the camera and placed in My Photos.
Comment
-
It's 338Kb - 984 x 1012 pixels.
Takes 1.07 seconds to process on my 1 year old Athlon 4400+ / 2Gb RAM system.
Normal product sized images take about 0.1 seconds each on that system.Norman - www.drillpine.biz
Edinburgh, U K / Bitez, Turkey
Comment
Comment