Timeline for What is your take: TimThumb vs. WordPress Thumbnails? The great debate
Current License: CC BY-SA 3.0
13 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Sep 10, 2012 at 10:53 | comment | added | Daniel Sachs | @YoavAner Most certainly. I didn't know either, but as a concept TimThumb "invites" such attacks, imho. This is what we, as developers, supposed to know. This isn't the reason for me not to use it, obviously, - only as a side note. I completely support your approach of "to each his own", but I think that, in general, the native function has less disadvantages. | |
Sep 9, 2012 at 19:24 | comment | added | Yoav Aner | I don't know who's to blame, I certainly didn't know about the vulnerability until it was published. The vulnerability was fixed, so I don't see this as a reason not to use timthumb, in a same way that wordpress has vulnerabilities, but it's not a good-enough reason to stop using it completely. As for the pros and cons of each approach, there isn't a silver bullet and it's fine. I prefer the dynamic aspects of timthumb and the DRY aspect of storing only one image (and not having to re-hash them when you change thumb size in your theme). Others may have different priorities. | |
Sep 9, 2012 at 10:22 | comment | added | Daniel Sachs | @YoavAner I have to disagree here, Yoav. Storing the the images locally may take a lot of a hardware space, but this isn't the bottle neck for most uses. CPU and Memory usually is, imho. Plus remember that TimThumb security breach back in January? This is serious. And by the way I blame us, the developers. We knew about TimThumbs vulnerabilities, but did nothing... I do think that FTP/Git upload is a nice feature with TimThumb, but it pales in my mind compared to disbandment | |
Sep 9, 2012 at 10:08 | comment | added | Daniel Sachs | @Damien. You're right, it's one of the disadvantages, among many, I guess... On the other hand it's easily addressed by editing the original file via WordPress image editing feature. | |
Aug 29, 2012 at 19:47 | comment | added | Damien | @Daniel there is one limitation on this function ... which is the crops are all from the centre. This is really bad if you have a headshot (like in Lucas's picture). However i agree this should be the best approach | |
Feb 7, 2012 at 13:21 | comment | added | Yoav Aner | @DanielSachs dynamic regeneration is one of the primary reasons I prefer timthumb. Also, I don't necessarily want to use the wordpress media uploader, and rather use FTP/SCP/Git. Timthumb also supports zc=2 option which I find very useful, and different level of compression. I find the way wordpress statically stores all thumbnail sizes inefficient, whereas timthumb just caches what's actually accessed with only one source version. | |
Aug 6, 2011 at 14:42 | comment | added | Otto | If you want dynamically created image sizes, I made a plugin for that: wordpress.org/extend/plugins/dynamic-image-resizer | |
Jul 8, 2011 at 19:36 | vote | accept | Lucas | ||
Jul 1, 2011 at 17:26 | comment | added | Lucas | Is there a reason this would only adjust the height and not the width? That's what it's doing with mine it seems. It is also failing to crop the images, it is just resizing them. | |
Jun 30, 2011 at 22:07 | comment | added | Daniel Sachs | Oh and one last note. If you add this function to an existing site your thumbnails will not be regenerated for past images, but you can use Ajax Thumbnail Rebuild plugin to rebuild the thumbnails for all the uploaded images | |
Jun 30, 2011 at 22:00 | comment | added | Daniel Sachs |
yes it's very nice I use it all the time. For instance: if you have a frontpage slider with some weird image dimensions jut add <?php add_image_size( 'weird-slider-main-image', 634, 74, true ); ?> and then all you need is to call it <?php if ( has_post_thumbnail() ) { the_post_thumbnail( 'weird-slider-main-image' ); } ?>
|
|
Jun 30, 2011 at 21:55 | comment | added | Lucas | I didn't even realize that function existed! | |
Jun 30, 2011 at 21:54 | history | answered | Daniel Sachs | CC BY-SA 3.0 |