The other day I installed the acidfree module & it worked well, including today when I uploaded a picture. A short while ago, I started getting this error message:

You must upload an image

even if I select an image. I have no idea what has triggered it. I disabled the acidfree module, and later uninstalled it, suspecting it had something to do with it, since I have never had this problem before, but even the image module alone gives that error when I try to submit.

How do solve this?

Comments

drewish’s picture

two things:
* try out the -dev release.
* try putting Drupal's temp directory inside the web root.

denishaskin’s picture

How stable is the -dev release? Ok for production use?

What do you mean by Drupal's temp directory? Do you mean the files directory? Or an environment variable?

I'm getting this problem on a completely fresh Drupal 5.2 install, no additional modules, just image 5.x-1.5.

Thanks... dwh

drewish’s picture

at this point -dev should be fine for production use. once there's a 1.6 i'd say use that unless you run into other bugs.

the temp directory set in admin/settings/file-system

markusH’s picture

Hi, I've got the same problem here. I'm using Drupal 5.2 and the most recent dev version. My temp dir actually is in the Drupal root directory (I tried both a relativ path and absolute) and it still give the error message. Any more ideas what we could try?

Brian@brianpuccio.net’s picture

I am having this same problem, as well. I get two errors, however:

The selected file /home/siteshomedir/web/tmp/tmp_UNq2KY could not be copied.
You must upload an image.

I've changed the permissions of the tmp folder, tried both relative and absolute paths and even tried using /tmp, hoping that would work. Same error every single time.

If you let me know how to debug this or whatever I can do to get you more information, I will do it.

Brian@brianpuccio.net’s picture

For what it is worth, the upload module has no issues at all.

Brian@brianpuccio.net’s picture

Last bits of info. I'm running head. I can regenerate the derivative images for already existing images, just can't create new.

Brian@brianpuccio.net’s picture

OK, I fixed this for myself by logging in as root and removing all temp and tmp directories located in the drupal root and any subfolder. I used the devel module to track down exactly the path to the file that it said was missing. It was not in /home/siteshomedir/web/tmp/tmp_UNq_2KY as the error had originally indicated. The devel module gave me a path of files/images/temp/filename.jpg, that it said it didn't have access to. I'm not sure why this happened and why the image module doesn't use the temp directory set in the file system administration screen, but the problem for me is fixed.

Hopefully others here will find this useful.

wla_g’s picture

I do have the same issue. When I try to upload a picture (test installation on my local system with Mac OS X) I get a white screen. I can find the picture later in drupal/files/images/temp/file.jpg, but thats all. Something in the handling of the transfer doesn't happen. As I'm new to Drupal, I've double checked the access rights ans they are ok (777 on files, images and temp) . I don't get any error message at all. Nothing is written in the log file. I'm using drupal-5.2, PHP 5.2.3, Apache 2.0.59. Any idea?

joel_guesclin’s picture

I am getting this same problem. The temporary file setting for Drupal is /tmp. I say that under the /images directory there was a /temp directory, so tried deleting this.
When I then went to try to create an image, as soon as I enter "create->image", I get the message that the directory "images/temp" has been created - so I don't have much choice in the matter!!
Then the image creation fails with the message "You must upload an image."
Looking in the images/temp directory, I can see that the different sized files have all been created - so the problem must come when it tries to copy into the "live" directory.

drewish’s picture

joel_guesclin, it sounds like you might have an open_basedir restriction that's limiting access to /tmp. try creating a temp directory inside your webroot and using that.

joel_guesclin’s picture

Version: 5.x-1.5 » 5.x-1.6

I upgraded to 1.6 and changed my file temporary directory to one inside my webroot - still no joy. Then I thought I would rerun the upgrade I had just done from 4.7 to 5.2 - suddenly it works! What happened? No idea!

wla_g’s picture

I've at least found how my issue starts:
I've a new database and the view and image module loaded, (drupal 5.3, image 1.6)
As soon as I load the German localization (enabled, but not default) I can't upload an image. The screen stays white (i.e. no html-code generated) the image itself ends up in files/images/temp but nothing else happens. Even if I delete this localization afterwards, the problem remains. Maybe this gives someone a clue, what happens.

Hetta’s picture

Status: Active » Closed (duplicate)