Rebuild Thumbnails after Easypopulate

[ridexbuilder]

I'll take the fifth on that para. - wasn't me that wrote that.
The name of that setting is historical (hysterical?) though and was probably clearer when there were no other 'Size' settings after that one.
Ponder over what it should be called?
Description in my words: where only a width or height is specified above, calculate the other dimension to retain the image proportion.

[msimplay]

Lol it's my fault for only reading the first bit of the page but it's also your fault for assuming a novice like me would catch on without hand holding.
I understand that it gets frustrating since you know the product inside out.

I say to make that wiki easier I would put as part of the Settings as

• Rebuilding Images after importing products ? Not yet see work around below

Or something like that just an idea

[ridexbuilder]

If producing a routine for thumbnail regeneration, server-side, there will always be an inherent limitation. Images_big would have to be used as the basis of the thumbnails, which are already in a compressed state, compared to loading (usually) larger images from the Admin. console. Admittedly, there may not be much difference visually but is something to consider.
It is still better to re-create both images_big and thumbs from the original source images. This has less loading on the server and less bandwidth usage during image uploads.
Many/most people have more processing cycles available at the local machine (PC), to batch process the image resizing. For example on an 'ageing' 1.4GHz Centrino with 1Gb RAM, Irfanview can batch convert 500+ images in literally a couple of minutes.

Just some thoughts.

[msimplay]

I have to agree with you here it didn't take me long but I'm new to the whole easy populate thing.
Just last year I started my own store online and I used to add every product individually through the admincp 1 by 1.

Also while I can say this method is better with regards to quality the difference is minimal and the big thing is that it reduces functionality that other carts already provide.
I understand that the project is free and open source but still you have to be competitive.

Although now having tried this method I'm reconsidering the way thumbnails are done on my own store when adding products in bulk.

[ridexbuilder]

Due to further enhancements in the upcoming release of 2.1, I've decided to take your wishes to heart. Actually, the motive is to make upgrading easier for the lazy.
I have written a routine to generate product thumbnails and product images from files found in images_big. [Notice: three image sizes].
Currently in alpha/beta and a few guinea pigs needed that use 2.1 SVN but on track to be a fairly useful tool, if somewhat resource intensive for larger stores. If you're currently storing in excess of 500 images in the main images_big directory (or worse, images directory ), then you might like to consider the one level sub-directory provision in 2.0.25

There is no intention to release this for 2.0.x, so if anyone wants this to be 'downgraded' for use on the older version(s), then it will be by donation only. Period. Another use might be to move all your existing large images into images_big and batch generate thumbnails - thus speeding your site up and gaining the benefits of Slimbox (now customisable).

EJ

[msimplay]

Due to further enhancements in the upcoming release of 2.1, I've decided to take your wishes to heart. Actually, the motive is to make upgrading easier for the lazy.
I have written a routine to generate product thumbnails and product images from files found in images_big. [Notice: three image sizes].
Currently in alpha/beta and a few guinea pigs needed that use 2.1 SVN but on track to be a fairly useful tool, if somewhat resource intensive for larger stores. If you're currently storing in excess of 500 images in the main images_big directory (or worse, images directory ), then you might like to consider the one level sub-directory provision in 2.0.25

There is no intention to release this for 2.0.x, so if anyone wants this to be 'downgraded' for use on the older version(s), then it will be by donation only. Period. Another use might be to move all your existing large images into images_big and batch generate thumbnails - thus speeding your site up and gaining the benefits of Slimbox (now customisable).

EJ

Lol thanks for making it easier for me (the lazy) it's very good news.
But seriously while as a web developer you may call it being lazy personally as businessman I call it ease of use.

My point of view is simply that I want to spend the least amount of time working on the basics so I can concentrate on the real meat and potatoes which would be the sales and customer service.

I think it was in a Magento webinar where it said something like "no need to feel restricted by the backend" and that's what I want and going on a limb maybe what everyone wants.

[ridexbuilder]

... "no need to feel restricted by the backend" ...

You can get suppositories for that!

[ridexbuilder]

PGM has got the bit between his teeth and "gone a bit Lara" with this concept. Oh no, look what ye've started! The routine is growing arm & legs by the hour. What was once my wee pet project has been swallowed up into a vast chasm, that is the coding prowess of PG Marshall - read was only a few Kbytes, now well who knows...? [Windoze bloatware users, eh? Gimme a command line any day]

[pgmarshall]

LOL - Haha ... Don't Windoze me ... currently considering a mac! (last time I had a mac was 20 years ago!)

Anyway, the file is still only 14Kb - so stop complaining !!

However, server load maybe quite high due to number of loops required to do all the checking for you ... but then again you are not going to run this everyday ...

Should do all sorts of checks for you ... when complete!

Nice to see Presta charging $50 for this (for the current level - never mind the extra stuff we are going to make it more functional ... )

Regards,

[ridexbuilder]

A Mac? Another proprietary system!
Big long trench coat a la Lt. Columbo, more like.