(For anyone tackling this: I assume this issue refers to the fact that image_imagemagick_settings() would need to be updated to conform to the FAPI in Drupal 4.7. This still seems to be case, and the needed change would be trivial. OTOH, it is very unclear exactly whether and how one is supposed to use this particular file with image.module, anyway.)
This issue belongs in the issue tracker for image.module, not Drupal core; moving.
This might be the problem that I am having too. I have no problem uploading images but after a while (usually a day or two) the thumbnails (or other size) for my images disappear and only the originals remain. A great example of this is if you go to one of my image galleries at http://chibabeat.com/image/tid/177. All of the pictures originally were 200x200 regular view but now it only has the original view for some.
My watchdog is showing a few different warnings. One is The selected image handling toolkit 'imagemagick' can not correctly process 'image_imagemagick_resize'.
Another one is getimagesize(): Read error! in /hsphere/local/home/chibabea/chibabeat.com/includes/image.inc on line 89.
Now the last error is really weird because I have the image handling set to ImageMagick.
I tried to install image_enhanced_resizer module which requires image.imagemagick.inc. When I installed the image.imagemagick.inc file in the includes folder, I set the default toolkit to imagemagick in admin/settings. This would generate errors when trying to create thumbnails. It would cause a white screen in admin/settings, so I could not change the toolkit back out.
To back-out, I needed to:
remove image.imagemagick.inc from the includes folder,
remove the setting imagemagick in the variable table in mysql,
restore connection to admin/settings,
copy image.imagemagick.inc back to the includes folder,
in admin/settings set the image handling toolkit to Built-in GD2 toolkit.
There is also a problem in that you cannot set the path to the imagemagick binaries. The default location is hard-coded to
/usr/bin/convert/
Comments
Comment #1
nyumbani_yangu commentedAre there any news in regards of this issue.. My image module is not working because I get the error about an image toolkit not properly setup.
Comment #2
Stefan Nagtegaal commentedWhat version of PHP is your server running?
Comment #3
Arto commented(For anyone tackling this: I assume this issue refers to the fact that
image_imagemagick_settings()would need to be updated to conform to the FAPI in Drupal 4.7. This still seems to be case, and the needed change would be trivial. OTOH, it is very unclear exactly whether and how one is supposed to use this particular file with image.module, anyway.)This issue belongs in the issue tracker for image.module, not Drupal core; moving.
Comment #4
orionvortex commentedThis might be the problem that I am having too. I have no problem uploading images but after a while (usually a day or two) the thumbnails (or other size) for my images disappear and only the originals remain. A great example of this is if you go to one of my image galleries at http://chibabeat.com/image/tid/177. All of the pictures originally were 200x200 regular view but now it only has the original view for some.
My watchdog is showing a few different warnings. One is
The selected image handling toolkit 'imagemagick' can not correctly process 'image_imagemagick_resize'.Another one is
getimagesize(): Read error! in /hsphere/local/home/chibabea/chibabeat.com/includes/image.inc on line 89.Now the last error is really weird because I have the image handling set to ImageMagick.
Comment #5
orionvortex commentedJust fixed mine by applying this fix http://drupal.org/node/71178#comment-147675
Comment #6
wylbur commentedI tried to install image_enhanced_resizer module which requires image.imagemagick.inc. When I installed the image.imagemagick.inc file in the includes folder, I set the default toolkit to imagemagick in admin/settings. This would generate errors when trying to create thumbnails. It would cause a white screen in admin/settings, so I could not change the toolkit back out.
To back-out, I needed to:
remove image.imagemagick.inc from the includes folder,
remove the setting imagemagick in the variable table in mysql,
restore connection to admin/settings,
copy image.imagemagick.inc back to the includes folder,
in admin/settings set the image handling toolkit to Built-in GD2 toolkit.
There is also a problem in that you cannot set the path to the imagemagick binaries. The default location is hard-coded to
/usr/bin/convert/
Comment #7
drewish commentedthe lack of follow up leads me to believe this is no longer an issue.