"The destination images/ is not properly configured" -- why? [#261226]

The process for saving an Image node, which worked on my local computer (Windows) does not work my client's host (Linux).

I get the following messages when I try to save a node:

* warning: move_uploaded_file(C:\DOCUME~1\JONATH~1\LOCALS~1\Temp\php\upload/06-04-01 Swedish ivy.jpg) [function.move-uploaded-file]: failed to open stream: No such file or directory in /export/home/webs/babylove/drupal/includes/file.inc on line 572.
* warning: move_uploaded_file() [function.move-uploaded-file]: Unable to move '/var/tmp/phpEwbO4P' to 'C:\DOCUME~1\JONATH~1\LOCALS~1\Temp\php\upload/06-04-01 Swedish ivy.jpg' in /export/home/webs/babylove/drupal/includes/file.inc on line 572.
* File upload error. Could not move uploaded file.
* The selected file could not be uploaded, because the destination images/ is not properly configured.

When I first tried this, I got a warning when I opened the editing page that the images directory was not writeable. I set permissions recursively to 777, and I no longer get that message. I checked the permissions of images/temp, and they are 777. Consequently it is not clear to me what "the destination images/ is not properly configured" means.

This looks suspiciously similar to a problem I reported after trying to use the Image Attach module on my local machine; see http://drupal.org/node/247386. I ascribed that problem to the fact that Image Attach had not been tested under Windows, but now I wonder if the two problems have common source in the fact that the image source is on a Windows platform.

Comments

Comment #1

orthoducks commented 26 May 2008 at 23:07

Later -- I discovered the "temp file directory" setting in on the Files page. It was set to the Windows temporary directory. I did not know it was there because I never had to visit it before; the installer must have set it automatically for my original (Windows) installation.

When I changed this setting, though, Image went right on trying to use the non-existent Windows temp directory. I tried clearing the cache; no change. What else is there to try?

Later again -- I revisited this setting and discovered that it was still pointing to the original Windows location. I changed it again; the change stuck this time; and everything worked.

I'm puzzled by this. The obvious explanation, that I forgot to click Save, is wrong. I just assumed that the Linux temp directory would be /tmp, and was concerned that Drupal would not accept that; I remember my feeling of relief when the temp directory pathname changed from red characters to black, which could happen only when I clicked Save. In any case it's working now, and I'm truly relieved.

Comment #2

ñull commented 15 September 2008 at 12:09

Version:	6.x-1.0-alpha1	» 6.x-1.0-alpha3
Category:	support	» bug

I add this comment because it is "on topic" but for what seems a different issue.

When you activate the module Image and Image import, then some folders are created automatically. When I go the the Image import tab, I see a warning that the folder needs to be created. Two issues here:

Created folders have the wrong permission making it impossible to create the missing folder. Never really convenient when only root can do that. It would better be set to 777.
Why doesn't Image import module creates its own folder, just like the main image module does?