jperezmedina / timthumb

Automatically exported from code.google.com/p/timthumb
0 stars 0 forks source link

Getting a CURL error on external image retrieval #223

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?

I go to one of my post pages where the related posts appear

Any link with no image shows the default 

The posts with images won't show them

The setup worked fine on my local host development setup but when I moved it to 
my production site on Media Temple no images.

The url's are there on the page and the images show in the posts themselves but 
the thumbnail is not produced.

Here is the page source:

http://www.dougberger.net/archive/2011/04/60-minutes-carried-big-corp-water-on-t
ax-rate-story.html

I've attached the server error log

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by voncadf...@gmail.com on 7 Aug 2011 at 9:37

Attachments:

GoogleCodeExporter commented 8 years ago
I'm using version 2 of timthumb on WordPress 3.2.1 self-hosted on Media Temple

Original comment by voncadf...@gmail.com on 7 Aug 2011 at 9:39

GoogleCodeExporter commented 8 years ago
Thanks, repro'd this and working on it now.

Original comment by mmaun...@gmail.com on 7 Aug 2011 at 7:58

GoogleCodeExporter commented 8 years ago
Please upgrade to the latest timthumb which fixes this error.

The version you're using is older and this issue was fixed yesterday. 
curl_close was being called before curl_error making the curl handle invalid. 

However your error message was useful because I've further improved the code by 
preventing errors from being written to the client if timthumb tries to delete 
a file that doesn't exist. 

Thanks for the bug!

The latest version is here:

http://timthumb.googlecode.com/svn/trunk/timthumb.php

Original comment by mmaun...@gmail.com on 7 Aug 2011 at 8:09

GoogleCodeExporter commented 8 years ago
Yes that update did fix the issue. Thanks. Only small issue was getting host 
name timeouts which is odd in general but I increased the curl time out value 
to 50 from 20 and that seemed to take care of that issue.

Original comment by voncadf...@gmail.com on 7 Aug 2011 at 10:42

GoogleCodeExporter commented 8 years ago
Thanks, I'll consider increasing the default.

Original comment by mmaun...@gmail.com on 7 Aug 2011 at 10:55