marshsu / timthumb

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

Timthumb 2.85 not working with wp 3.3.1 and php 5.3.8 #321

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Hi 

I had a problem with the latest timthumb.php v 2.8.5 with php 5.3.8 and wp 3.3.1

i got this error all the time A TimThumb error has occured

The following error(s) occured:
Could not find the internal image you specified.

Query String : 
src=http://mywebsitename.com/wp-content/uploads/2012/01/banner.jpg&w=940&amp
;h=320&zc=1
TimThumb version : 2.8.5

but the image was there and permissions where ok.

i had to modify the line 853 to get it to work again.

i changed

if(stripos($real, $this->docRoot) == 0){

into 

if(stripos($real, realpath($this->docRoot)) == 0){

Could you please look into this. It works now on my server, but without the 
changement it also works on php 5.2.1 with wp 3.3.1 but not on 5.3.8 with wp 
3.3.1

Looking forward to your reply,

Best regards,
N.

Original issue reported on code.google.com by neo.al...@gmail.com on 15 Jan 2012 at 10:55

GoogleCodeExporter commented 9 years ago
I had the same issue and your help worked for me.. changed the same line to 
what you suggested and it worked.

Original comment by mikulamu...@gmail.com on 25 Jan 2012 at 3:48

GoogleCodeExporter commented 9 years ago
Apparently there is more version of the timthumb 2.8.5 circulating on the web.

i found one in another website dealing with this problem completely different. 
However they could not reproduce the link they had downloaded that version from.

so 10 days after lauching my problem here not a single reply from the author.

I would like to know if my fix is the right way to handle with this problem.

Original comment by neo.al...@gmail.com on 25 Jan 2012 at 5:55

GoogleCodeExporter commented 9 years ago
Hi - this isn't a support forum - I do this part time so can not afford to 
spend lots of time monitoring it.

Please try the latest version of TimThumb - committed yesterday. It should 
hopefully fix this issue.

Original comment by BinaryMoon on 8 Feb 2012 at 11:47