Hi Rahe,
I find it limiting when it comes to specific parameters, i.e. cropping, image quality, background fills, etc. Hammy is something created from client projects, in which we always use WPThumb. It’s simply not feasible to have to regenerate 100’000 images every time you want to test a different breakpoint, etc. The impression I get is core contributors actually like the concept of phpthumb (which WPThumb is based off), but feel it would be too bloated/too much for the regular WP user. At the end of the day, a lot of it is personal preference 🙂
Cheers!
Noel
Hi,
I am agree with the fact of the WordPress API is limited, but there is no garentee that WP_Thumb will continue to work in further WordPress updates :/.
The image API will be, one day maybe, updated but for the moment you do not change your breakpoints, image sizes at any time in your website, the sizes are made on the conception of the website so you do not regenerate the images at any time. Plus the timthumb solution have opened security breaches on many websites and themes. It’s safer to use the WordPress API, even is it is not complete.
The ultimate solution is to not generate the sizes when uploading an image but when you need it, so the ressources are preserved and the disk space. The plugin http://wordpress.org/extend/plugins/dynamic-image-resizer/ try to make this but there is a bug and the images are not quitely generated…
I hope there will be a real update on this point, especially because of the reponsive problem and the retina etc.
🙂
Rahe
Hi Rahe,
We created WPThumb (humanmade) and even use it on a site with 15 million unique’s monthly. If the theme changes, all those sizes need to be regenerated. WPThumb is not TimThumb, so I don’t quite understand that point, sorry :/ WPThumb creates the additional image sizes when the original image is loaded for the first time on any page (which is why when we changed the theme on the site with 15mil unique’s, there was no issue).
Cheers
Noel
Hi,
Your last message was like saying that WPThumb is based on TimThumb, my bad ;).
This solution could replace the WordPress core functionnality with hooks and filters, maybe there is a solution here.
Sorry for the misunderstanding ;).
Rahe
