Images upload but don't display because they are corrupted

Hi, thanks for your help.

I checked my php.ini, and the error logging is set to E_ALL.

However, no errors are being generated in the log, just a warning from a module I have written that has nothing to do with images:
"Warning: Call-time pass-by-reference has been deprecated - argument passed by value; If you would like to pass it by reference, modify the declaration of [runtime function name](). If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file. However, future versions may not support this any longer. in /var/www/html/yaq/modules/centro_edu/centro_edu.module on line 27"

I have done as you suggested and tried to save the image. It appears to do the save, but when I look in the directory I have saved to the file is not there. If I look in the download manager at the entry for the download just attempted, and click on "open", I get the message "File does not exist. It may have been renamed, moved, or deleted since it was downloaded".

Perhaps if I knew if it is Drupal or another program that generates the "The image “http://www.yaq.lan/yaq/system/files?file=images/Chico_interrogacion.thum...” cannot be displayed, because it contains errors." message, that might help me to look for clues? I checked the Drupal error log, but no events are created upon loading the page, nor on trying to view or download the image.

Hello again,

Here's what I did:

1) Right click on the text (caption) that shows up where the image should be, and choose "Save image as" from the context menu (save page doesn't seem to show up as an option).
2) A "save image" dialog appears, allowing me to choose a name for the file (I write in "test.jpg") and a directory to save it to. I click the "save" button on this dialog.
3) A "downloads" dialog appears, with a list of all my recent downloads. "test.jpg" appears as "done". To the right of "test.jpg" appear two links: "open" and "remove".
4) I click on "open", and get the message: "test.jpg does not exist. It may have been renamed, moved or deleted since it was downloaded.

It seems as though drupal isn't returning a file at all, but it's strange as no error messages (that I can find) have been generated.

Are there any other tests I might try that could shed some light on what's going wrong?

Thanks again for your help.

Steve

If I put this URL into firefox: file:///var/www/drupal_downloads/images/Chico_interrogacion.thumbnail.jpg

It displays the picture in the browser window with no problem. It wouldn't appear to be a firefox problem.

My gut feeling is that it's some environmental (apache or php) or drupal configuration problem that prevents the Drupal file system from retrieving files from the download directory. If I could only find an error message somewhere...

Text files are working. I created a simple text file and uploaded it to a page node. Then navigated to the page, clicked on the download and it downloaded perfectly to my desktop. I could open the downloaded file without problem.

Well, the results are interesting. By the way, thanks to you guys for taking time to help me with this.

I must admit I had never heard of curl, as I'm a little new to all this, but I think I have what you asked for. I tried 2 commands, which I'll repeat here so you can see exactly what I typed:

1: curl -i http://www.yaq.lan/yaq/system/files?file=images/Chico_interrogacion.thum... > yaqhead.txt
2: curl http://www.yaq.lan/yaq/system/files?file=images/Chico_interrogacion.thum... > yaq.jpg

I don't know enough to interpret the header, but the interesting thing is that the yaq.jpg seems to be my image file. I can open it with gimp, and also with the gThumb Image Viewer. That just makes my problem seem all the weirder.

The header file I was only able to inspect doing "more yaqhead.txt". Gedit wouldn't work on it.

I've attached both files so you can take a look.

Very strange and interesting....

I installed the toolbar, and looked at the header as praseodym suggested (text file attached), and I did see that the gzip type was in use. This reminded me that I had enabled the ob_gzhandler at one point in the php.ini. So I disabled it, and... that didn't solve the problem. However, all of a sudden, I started getting errors in the error log.

Type php
Date Thursday, April 6, 2006 - 17:10
User arrigenna
Location /yaq/admin/modules
Message Cannot modify header information - headers already sent by (output started at /var/www/html/yaq/modules/centro_edu/centro_edu.module:275) in /var/www/html/yaq/includes/common.inc on line 192.
Severity error
Hostname 192.168.1.51

Before I had only been getting warnings, but not in the watchdog, only in the php error log:

[client 192.168.1.11] PHP Warning: Call-time pass-by-reference has been deprecated - argument passed by value; If you would like to pass it by reference, modify the declaration of [runtime function name](). If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file. However, future versions may not support this any longer. in /var/www/html/yaq/modules/centro_edu/centro_edu.module on line 275
[client 192.168.1.11] PHP Warning: Call-time pass-by-reference has been deprecated - argument passed by value; If you would like to pass it by reference, modify the declaration of [runtime function name](). If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file. However, future versions may not support this any longer. in /var/www/html/yaq/modules/centro_edu/centro_edu.module on line 287

I had thought that the warnings about deprecated syntax only meant I should be aware that the code might not work for future versions of PHP, but for the time being wouldn't give any problems. So it didn't occur to me that this could be related to the image problem. After turning off the ob_gzhandler, the warnings turned into errors, and still related to the same module: centro_edu.module (one of my first attempts at writing a module). I turned off the module, and the images now display properly. I must admit, I don't know what the interaction was that caused the problem.

So I guess my next step is to rewrite my module to eliminate the deprecated syntax.

Thanks very much for all your help!