"cannot save file" issue again

This issue is not really a bug, so I mark it as "support¨.

Please note that 4.3.0 is not used too often anymore, so I don't think anybody will be able to help you by reproducing the problem. Neither can I check it, because I have no more sites running 4.3.

That might also prove to be the solution for you: upgrade to 4.4.2 with the appropriate image module. The whole upload system has changed since 4.3.

Another quick solution could be to set the tmp directory on a web-accessible place and point towards that place. You might suffer from resrtictions set on the host.

Regards, Bèr

try using a flat file structure.

/images
/thumbs
/tmp

make sure to set permissions 777.

this module needs a maintainer and someone to update the instructions. i see this question 3 or 4 times a month. i'll be able to help some but not right away. does anyone know or have a reference to what the current status is on image handling in cvs? is anyone working on something?

i don't remember if it matters but i have it relative to my drupal install. the idea is to move the thumbs and temp directory out of the images directory.

in my images configuration page this is exactly what i have entered:

images/
thumbs/
tmp/

which is in my drupal install.

that was a bummer. A mayor tyo made me type 4.3 instead of 4.4. I am sorry. Extremely. My comment, however (for 4.3) is still valid, for it was typed for 4.4.

I had the same problem, its not chmod 7777 what caused the problem with me it was lack of proper installment of imagemagik and gd library. One of these must work 100%, jhead is I think only used to post an image not to manipulate it which you require if you want thumbs automatically done...

I use imagemagik now and its important the convert dir is correct...

Hope this aids...

I'm getting this problem too. The module has worked in the past on other Drupal sites, but not on two that I'm developing now.

Using image module CVS and the latest Drupal CVS, I get errors about opening and renaming images on upload. Other modules that upload files (like node_image and filestore2) work correctly.

I've tried GD2 and IM, tried changing the paths to a flat structure and using absolute and relave paths, and have checked the permissions on the directories. I've recreated the SQL table and tried the suggestions posted in the issues for this project.

Help?

Sorry about the follow-up on my previous issue, but I've just noticed that the current error I'm getting ("Unable to open image" in a regular Drupal message box) is pointing to a file that exists in the Image module temp directory, so the file is getting uploaded (with permissions 644) but the module can't read or find it.

Help^2.

exactly the same problem as others have described.

drupal 4.4, same thing, the images are being uploaded, but the tmp and thumbs aren't there, and the error keeps coming up:

warning: rename(images/tmp/tmpthumb_oldaptbldg.jpeg,images/thumbs/thumb_oldaptbldg-1137.jpeg): No such file or directory in /var/www/html/drupal/modules/image.module on line 719.
Cannot save image.

i tried moving the directories around so they were more flat, all in the drupal base dir. i triple checked ownership and permissions, chmod 777 for all of them. (as i said images are going into the images dir, and are there on the preview, i just can't 'submit' them.)

i tried dropping the empty image table and recreating it.

i've checked and all seems OK with my ImageMagick-6.0.0 convert script and the path to it seems named correctly.

any other ideas welcome!

regards,
-=pj=-

www.nefac.net

I just solved my problem from the error message, Unable to open file tmp/tmpimg.....

I had my program paths set properly, and got the following errors.

Default image path
OK
Default thumb path
OK
Temporary image path
OK
ImageMagick convert
DOES NOT EXIST - fix in Site Configuration
imlib2 library
unavailable
GD Library
available (version 2) - supported formats: JPEG, PNG, WBMP
Jhead
DOES NOT EXIST - fix in Site Configuration
Image vocabulary
assigned

So I disabled jhead and ImageMagick, and was using GD2.

It appears GD2 does not work properly - creating the errors upon thumbnail creation.

I had my site admin reinstall Imagemagick and jhead, and I set the paths appropriately (again).
The module works normally now now that I have ImageMagick and jhead running.

However, I still get the DOES NOT EXIST errors. If I didn't just try the module on a lark, I probably would have thought that the module was still broken.

I am using the cvs image.module 1.116 and drupal cvs.

I'm using drupal cvs and image cvs and having the same thumbnail creation problem on a win2k/apache box.

I also have drupal 4.42 installed and the 4.0 image module works fine.

In the cvs version of image, there is no configuration option to choose gd or imagemagick.

i tried cvs 1.116 and 1.118, and they both produce the same error.

If you use 1.116 and select GD2 instead of imagemagick, you get a different error:
unable to open image temp/tmpimg_imagename.jpg

even though that temp image was created.

on windows, the imagemagick binary installs itself in c:/Program Files/

The space in the directory path screws it up, so instead, install imagemagick in c:/image or some other directory without a nice short name with no spaces.

Now image v 1.119 is working with CVS on my machine.

Doesn't appear to support GD2 anymore, though.

Sorry about that.. I am the post above.. Thought I was signed in. How is it possible this module has this many repeated and intractable problems. Is it something about Imagagemagick that makes it a moving target even within analogous Drupal installs?? I've read similar complaints going back a year.. There has never been a definitive answer but taking the ability to configure the path to convert doesn't seem to be the fix unless there is a foolproof configuration and path sensing script somewhere in in this CVS version. Why not come up with some kind of self contained image processing for Drupal if using imagemagick remains such an unreliable way to go. GD is an unreliable way to go as well but we know that..

By the way i'm on RH9 and MySql 4.20 standard. Not Windows anthing so these problem are not something confined to Win. The fourth post above would seem to be an answer ONLY THERE IS no way the Configure GD or Imagemagich in latest CVS version of Drupal.. I tried backing down to 4.42 image moddule but the same deal.

if you install cvs version 1.116 you can set the path. then you can install the latest verson over it. The path will still be there in your database variable table.

There was a lot of new code and a new file added to teh module between 1.116 and 1.119, so it must have got lost in the shuffle.

Can you reproduce with 1.120? All of the changes made from 1.116 to 1.120 were tested using Apache on Windows XP.

I am having the same problem that everyone else is having with submitting an image with image.module. I am using drupal 4.4.2 and the cvs version of image.module. I get the same "warning: rename(images/tmp/tmpthumb_ab993eb07c0fec5de1fbf77ab5bb8c25.jpg,images/thumbs/thumb_ab993eb07c0fec5de1fbf77ab5bb8c25-18.jpg): No such file or directory in /Library/WebServer/Documents/drupal/modules/image.module on line 719."

I pulled the following out of my Apache error_log "convert: no decode delegate for this image format `images/tmp/tmpimg_ab993eb07c0fec5de1fbf77ab5bb8c25.jpg'.
convert: missing an image filename `images/tmp/tmpthumb_ab993eb07c0fec5de1fbf77ab5bb8c25.jpg'.
[Mon Aug 23 10:17:19 2004] [error] [client 127.0.0.1] File does not exist: /Library/WebServer/Documents/drupal/images/tmp/tmpthumb_ab993eb07c0fec5de1fbf77ab5bb8c25.jpg"

Looks to me like the wrong syntax is being sent to convert to create the thubmnail. I'm no PHP expert, but I'm going to dig into the module to see if I can figure this out. If this gives anyone else any ideas, let us know.

OK. I'm a moron. My previos error was because I didn't compile jibjpeg before I installed Imagemagic. So, I'm recompiling now and will update later.

don't call yourself a moron just yet crford. wait a little bit and then...(jk).

well, so many people have this problem that what you forgot to do might have forgot to do as well. so it is important you mentioned this.

i would like to request that we add test images to the image module. one gif, jpeg, png and bmp. and also include an updated help file. i'm going to do that right now and post it here or a new thread.

I experienced the same error when using ImageMagick. I am running Drupal 4.4.2 on Win2K with PHP 4.3.1 and was using fast_cgi. Apparently there is a bug with file paths and fast_cgi - the fucntion file_exists() would only work on paths within my web directory. I changed permissions and I tried relative paths; it would not work and a test script worked fine with php-cli on the console. So I changed to CGI and then to ISAPI and in both cases ImageMagick worked fine. I know... another reason to move to Linux/Apache, but I'm not calling the shots on our Intranet. I hope this helps some Win2K users.

It seems to me that the image module problem is largely that it doesn't do any checking to see if the image handler (image magick or gdimage) is present. There needs to be a test when you save settings and if something is wrong there should be a bit of error flagging, i.e. "WARNING: path to image magick is incorrect or image magick is not installed". That would enable people to use the image.module more easily.

If stuff is part of the core it should not be difficult to install.

I agree on the need to have a validation that ImageMagick is installed correctly to get the image.module to work in Drupal 4.5.

This solo thread provided the right insight after about half a day of googling and testing variations on my first installation of 4.5 (formerly a phpNuker, formerly a self-coded perl site).

I am adding the following information to this comment to help other googlers find this information.
warning: rename(images/temp/tmpthumb_116_1623_s.805.jpg,images/thumbs/thumb_116_1623_s.805-16.jpg): No such file or directory in /home/username/public_html/dru/modules/image/image.module on line 827.

warning: Cannot modify header information - headers already sent by (output started at /home/username/public_html/dru/includes/common.inc:406) in /home/username/public_html/dru/includes/common.inc on line 217.

SOLUTION: change your ImageMagick path. I had it pointed to a bad installation but changed it to "/usr/local/bin/convert" for my particular shared server on Lunarpages.

This is one of those "misdirected" error messages and a lot of wasted time verifying paths created, proper chmod, etc.

hey there...

Someone posted the DOS 8.3 path of image magick as:
c:\progra~1\ImageMagick\convert.exe

This is not the case, as imagemagick is 11 letters. should be
c:\progra~1\ImageM~1\convert.exe

if my DOS memory is correct...

question: I would guess that some shared hosting accounts give you access to see the path of imagemagick (on unix this is /user/bin/convert) and some do not. I am using Dreamhost, and my shell account can see it. what about the rest of you?

-rich

i can't tell you how frustrated i am with this. i'm getting the same error, and of the many many threads on this issue i've read, there is not a single definitive answer as to what causes it, or how to fix it.

i'm on a freebsd box, php4.3.10, mysql4.0.x, drupal 4.5.1, and the latest image.module from drupal.org. i have chmodded 777 tmp, thumbs, and images directories in several places (it's an obscure mystery from the docs what is considered the "root", and why the tmp dir is supposed to start with ./ , when thumbs and images don't). the module status reports OK for everything, and imagemagick and gd2 are both installed and working. i have root on the server so i can put stuff anywhere it needs to go - just say the word.

so, can somebody please spend 3 minutes and please update the documentation on how to install image.module - please - the current docs are either missing something, or are just plain wrong...or this module is just buggy. did i say please?

in any case it is not up to the standard of excellence that folks like me have come to expect from drupal. it should not be in the core, particularly considering the dozens of people having identical or similar problems, and have been reporting them for more than 8 months.

does anybody know how to make this module work? i would be VERY grateful for a step by step, or should i consider this a no longer supported, dead module?

sorry for the rant, but hours after starting what i thought would be a 10 minute install, i've still gotten nowhere.

thanks,

srs

i'm trying to clean up the image module's issue queue. this issue looks like it's been resolved by more recent versions of the module. feel free to re-open this if you disagree.