On every page I see the error "Unable to create scaled thumbnail image".
So I thought maybe the permissions are incorrect.
/home/files/* have permissions of 777 so that's not the problem.
Then I took a look at the Image Toolkit (the image.imagemagick.inc file was copied to the includes folder)
When I try to use the ImageMagick Toolkit, I get the error:
"/usr/bin/convert does not exist."
I know for a fact that /usr/bin/convert exists.
When I try to use the Built-in GD2 toolkit, I get the same error. So then I try to remove the "/usr/bin/convert" because GD is called by PHP anyway, but I get the error "Location of the "convert" binary field is required."
Why isn't Drupal recognizing ImageMagick? Or GD?
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | phpinfo().html | 12.12 KB | HarryCambs |
Comments
Comment #1
drewish commentedi'm not sure what your original problem is but you've now run into: http://drupal.org/node/137755
Comment #2
drewish commentedi'd make double sure that the file exists where you think it does. it should warn you if PHP's open basedir restriction is preventing you from accessing the file...
Comment #3
kikr commentedhttp://drupal.org/node/137755 allowed me to change back to GD2, but I would like ImageMagick to be able to work too. Using GD2 gets rid of the "Unable to create a scaled thumbnail image" error.
[~/public_html/files/images]# which convert
/usr/bin/convert
[~/public_html/files/images]#
[~/public_html/files/images]# ls -ls /usr/bin/convert
8 -rwxr-xr-x 1 root root 4608 Feb 16 06:36 /usr/bin/convert*
[~/public_html/files/images]#
/usr/bin/convert is exists. I just don't understand why Drupal doesn't recognize it.
I want to use ImageMagick because it seems like GD2 is not resizing the images properly.
Comment #4
HarryCambs commentedI am also getting the same issue after upgrading from Drupal 4.6.
I cannot use GD because I am running out of memory and I cannot set the PHP memory limit because I have shared hosting.
Thing is that I have a second site using Drupal 4.6 on the same account and that seems to work fine with the image module, so must be something new causing this issue.
Comment #5
drewish commentedwell, take a look at this thread and see if it won't help you track down why we can't access the convert binary: http://drupal.org/node/131305
basically, it boils down to, install the devel module and run this:
Comment #6
HarryCambs commentedOk I get this:
bool(false)
bool(false)
Attached my php info as well in case it helps.
Comment #7
drewish commentedHarryCambs, yeah it looks like the open_basedir restriction is getting in the way. it should say as much in the error message.
Comment #8
HarryCambs commentedThanks, finally fixed by asking my hosting provider to remove the damning open_basedir !
Comment #9
rvens commentedI tried all suggestions placed here, but I still am not able to reset to the GD2 toolkit.
What did I do?
- commented out the lines in imagemagick include file
- tried to set to GD2
Also php safe mode is not enabled on my server, and imagemagick is installed on the proper location, and still drupal refuses to see it, and warns me with the basedir warning (which I am assured by my isp is not enabled on the site). So I am kind of stuck here. Hope someone reads this.
Comment #10
drewish commentedthe GD selection was fixed as part of another issue. make sure to update your .inc toolkit.
Comment #11
Camus-1 commentedI don't have ImageMagick and the built-in GD2 toolkit is reportedly installed and working properly.
I'm getting the "Unable to create scaled thumbnail image" error ever since I upgraded to Drupal 5.1.
Google for "Unable to create scaled thumbnail image" and with the over 3000 results, I believe I'm not alone in getting this error message.
I would be glad if anybody could point me in the right direction for me to solve the problem. Thanks in advance.
Comment #12
drewish commentedCamus, well it's a pretty generic search string. Searching for Drupal "Unable to create scaled thumbnail image" returns only 337 links...
But in either case, are you running the new 1.3 release?
Comment #13
Camus-1 commentedHi drewish,
First of all, thanks for your help and for creating an excellent module. FYI, I upgraded Drupal 4.7 straight to Drupal 5.1.
I've just upgraded the Image module to 1.3 (dated July 2, 2007) and I'm still getting the "Unable to create scaled thumbnail image" error.
Applying the patches dated July 3, 2007 did not solve that specific problem either. TIA.
Comment #14
Urfin Juss commentedYour mistake because of ImageMagickToolkit. Switch on GD2 and RebuildImageThumbnail. Success.
Comment #15
Camus-1 commentedUrfin Juss,
I don't have ImageMagick installed or selected. I'm only sticking with GD2.
I'm also getting the "Unable to create scaled Thumbnail image" error when I try to "Rebuild Image Thumbnail."
Comment #16
drewish commentedcamus i think your issue is http://drupal.org/node/142178 please make a backup of your database and image files and try out that patch.
Comment #17
Camus-1 commentedI started a fresh Drupal 5.1 site on the same LAMP server, with Image Module 1.3 and I'm getting the same error. So, I'm suspecting that it's something to do with my Apache or PHP configuration. I'll be posting more details on the config once I've gathered them.
Comment #18
Camus-1 commentedHere's my phpinfo
Glad if anybody could point out if I have configured anything wrongly. TIA.
Comment #19
drewish commentedCamus, if you don't at least acknowledge trying the suggestions i've given i'm going to stop responding to your comments.
the "in my Image toolkit page I can see: No image toolkits found. Drupal will use PHP's built-in GD library for image handling.
and in log: GD library bundled (2.0.34 compatible)" message is fine.
also, marked http://drupal.org/node/157042 as a duplicate of this.
Comment #20
mysocom commentedI deleted my existing image module with a lot of pathes then
Installation of patch don’t have error. Only “patching file image.module”, “patching file contrib/image_import/image_import.module”.
But problem still there and now there are a lot of msg in log: “The selected image handling toolkit GD2 can not correctly process image_GD2_resize.” And of course in every node I have my favorite Unable to create scaled Thumbnail image
I can’t find image table in a database. How can I delete image module completely and start from the beginning?
Please, don't give up!
Comment #21
Camus-1 commentedDear drewish,
I apologize. My bad.
I did try the patch you suggested but it didn't solve the problem.
Thanks and regards,
-Camus
Comment #22
drewish commentedmysocom, it sounds like your GD library is messed up... you should see if you can use the imagemagick toolkit on your server.
Comment #23
Camus-1 commentedMy problem is fixed now. I ran gd_info() command and I just realized that my GD2 installation did not include jpg support. GIF and PNG images were working fine, and the error only crops up when the image is JPG.
I have since added the JPG support to the GD2 and the problem is now solved. Perhaps the module could provide indication at admin/settings/image-toolkit to list down all the image types supported by the specific image toolkit as specified by gd_info().
Thanks all, especially drewish. I am now a happy camper. :)
Comment #24
drewish commentedCamus, glad to hear that. I'm going to close this up.
Comment #25
Z2222 commentedI'm having the same problem -- cannot create thumbnail images. I'm using a clean installation of 5.1. I upgraded the Image module to version 5.x-1.4 (July 10th, 2007) and ran update.php. It still cannot create thumbnails. My PHP has GD support but no Imagemagick. GD jpeg support is enabled. I'm having this problem on a couple of sites, both on Site5 Hosting.
Comment #26
drewish commentedguitarmiami, go ahead and open up a new issue. please post as much detail as possible.
Comment #27
Stefan Nagtegaal commentedWas PHP compiled with safe_mode On? (You can find out by doing php_info() inside a php page.
Please let us know..
Comment #28
(not verified) commentedComment #29
Z2222 commentedPHP safe_mode is off.
I'll open a new issue.
Thanks
Comment #30
omar alahmedthanks Camus #23, yes it was GD2 problem, the jpeg images wasn't enabled successfully.