Up to now I worked with the Image module and ImageMagick and had not problems.
But now I want to add a Images to other nodes too. So I installed the Imagefield module and because of the dependency the ImageAPI module too. In ImageAPI I enabled the ImageMagick toolkit. That means that ImageMagick is now enabled in the "Image Toolkit" (Drupal Core) as well as in the ImageAPI.
Every time I upload an image with Imagefield I get the error-massage (which comes from the image.imagemagick.inc):
ImageMagick reported an error: convert.exe: no encode delegate for this image format `[pathtodrupal]\files\temp\tmp1AC.tmp'.
This message disappears if I disable ImageMagick in the "Image Toolkit".
Any ideas what could cause this error? [I am not sure if this is the right place for this bug report. If not, please feel free to redirect me to the proper place.]
Comments
Comment #1
ivanmilos commentedThis is some kind of a problem with newer versions of ImageMagic (6.4.x). I run into it myself, and the only solution I found was to install an older version (I now run ImageMagick-6.3.5-Q16). I read about it on ImageMagick forum: http://tinyurl.com/cgtyd5
Obtaining an older version binary release might be a problem because imagemagick.org and sourceforge serve only source code for older versions. I managed to find a download link only via P2P (eMule).
Comment #2
smitty commentedThat's no option fpor me, because my provider provides only the newest version of ImageMagick.
Is there anything we could do in the ImageAPI, the Image Toolkit" (Drupal Core), the imagemagick.inc ... ?
Comment #3
ivanmilos commentedWell I suppose some part of the ImageMagick Advanced Options module should be rewritten. I'm no coder myself so I have no idea how big an issue this is. Oh, btw I'm using drupal 6 so this is not an isolated drupal 5 issue. I'll drop a note to the guys that originally developed the module.
Comment #4
smitty commentedGood idea! I'm looking forward to their response.
Comment #5
drewish commentedi think the problem is that imagemagick isn't able to find the file type because the extension is .tmp. i the image.module's imagemagick support is really the code being called here.
i'd be tempted to mark this as won't fix since there's not something obvious we can do about it.
Comment #6
sunRelated: #219261: Force conversion of images to specified format
Comment #7
smitty commentedSo the question is: Why is there a temporary file-name and a temporary extension (.tmp)?
Could this be fixed by keeping the original file-name in the Imagefield module (like it is done in the image module too)?
Comment #8
webrascal commentedThe temporary filename and extension is setup by the server. The file is uploaded to the server temp directory almost like you would put things into a holding pen, and then the code in question is supposed to interact with that file as necessary.
I found it simple enough to test the tmp file using image_get_info to get an easy fix in for our project.
You can see it in #219261: Force conversion of images to specified format
Comment #9
sunComment #10
sunMoving to ImageMagick project.
Comment #11
andypostprobably this could be fixed by adding
-identifyto command lineComment #12
sunActually, I don't think this issue exists in the current code anymore.