Image Resize

This sounds like an image toolkit problem. Are you sure your toolkit is set up correctly? Go to admin/settings and check. Which toolkit are you using?

Do your apache logs give you any errors? Maybe you are running out of memory?

I'm having the exact same problem on the Linux production box I'm setting up (I didn't see this earlier Mac OS X box I used for experimenting.)

I'm running Drupal 4.6.5 on a Redhat Linux Box with Apache 1.3.3, PHP 4.3.11, and MySQL 4.1.12. I've got filemanager.module, the Acidfree patch for that module, and Acidfree installed. Everything has plenty of memory -- although PHP had been set to 8MB max memory for a script, upping it to 32 made no difference. Also, no errors were written to the Apache error log, so it looks like it thinks everything is cool.

The program does create the three files (thumb, small, large) in my /files/private/active/0 directory, but they are all the same size. On my previous install, I was running PHP 5.0.4 -- not sure if that would make a difference. THe other big change (aside from the underlying OS) is who "owns" the files; on the Mac box I cheated and set the permissions to 777 and didn't change the owner; on the live box, the Apache user and group owns the /files directory and its contents. Given that the files *are* being created, I don't think the problem lies there though.

I'm inclined to think it has something to do with the GD install, but I'm not sure how to go about testing that (never having worked with that tool before).

Here are the results of my acidtest config report:

Acidfree self-test checklist
Filemanager module enabled
Latest version of Filemanager module installed
filemanager-private.patch applied
Filemanager private path set and permissions OK
Filemanager public path set and permissions OK
Filemanager database table created
Acidfree class definition files found for album, photo, video
Drupal 'Temporary directory' path set and permissions OK
Acidfree database tables created
gd image toolkit installed and properly configured
No errors were detected. But this doesn't mean that Acidfree is guaranteed to work flawlessly. It is a complex system and still under development. Please be patient while all the wrinkles are found and ironed out.
PHP configuration

Maximum file upload size is 2M (upload_max_filesize)
Maximum POST size is 8M (post_max_size)
Maximum execution time is 30 seconds (max_execution_time)
Maximum memory usage is (32MB memory_limit)
If these limits are smaller than the files you plan on uploading, you should change the settings in your php.ini file

I'm 99% sure I've figured out this problem. It lies with the way the GD module was compiled; namely it did not include JPEG support. In order to determine what support your GD module has, create a PHP page with this code:

$gd = var_dump(gd_info());
print_r($gd);

Doing so on my machine created this dump:

array(10) {
["GD Version"]=>
string(27) "bundled (2.0.28 compatible)"
["FreeType Support"]=>
bool(false)
["T1Lib Support"]=>
bool(false)
["GIF Read Support"]=>
bool(true)
["GIF Create Support"]=>
bool(true)
["JPG Support"]=>
bool(false)
["PNG Support"]=>
bool(true)
["WBMP Support"]=>
bool(true)
["XBM Support"]=>
bool(true)
["JIS-mapped Japanese Font Support"]=>
bool(false)
}

To test my theory, I tried uploading a PNG file and it worked perfectly -- everything resized just fine. It's odd that GD doesn't throw any errors when it encounters a file it's not configured to handle.

vhmauery -- perhaps this is something worth adding to your acid free config test? In addition to testing for the GD module, you could execute that function and dump a list of "GD supported formats". I'm going to add JPEG support to the GD module and see what happens, but I'm certain that's the fix that's needed.

Ken

I am not sure that including that information is my responsibility. I think that kind of information should be listed when the toolkit is enabled on the admin/settings page. Each toolkit should have code for determining the supported image formats.

While you were determining that, I wrote up a little ditty for testing the current toolkit (be it GD, imagemagick, or whatever) So I am attaching that test file.

Tmortn, does any of this help you?

Tmortn:

Test out the toolkit_test.php file I posted. It will check to see if the toolkit is actually the problem so we can better determine where the error lies. Put it in your drupal root dir and point your browser at it. Without any args, it will print out the syntax. Try something like:

http://yourhost.dom/toolkit_test.php?img=path/to/image.jpg&resize=200
or
http://yourhost.dom/toolkit_test.php?img=path/to/image.jpg&resize=200&ro...

The path to the image should be a relative or absolute path to an imagefile on the server. Without the resize or rotate commands, it will simply stream the image.

if you do something like:

<?php
    phpinfo();
?>

and scroll down to the major subheading GD, you should see something that looks like

+----------------------+-----------------+
|  GD Support          |  enabled        |
+----------------------+-----------------+
|  GD Version          |  2.0 or higher  |
+----------------------+-----------------+
|  FreeType Support    |  enabled        |
+----------------------+-----------------+
|  FreeType Linkage    |  with freetype  |
+----------------------+-----------------+
|  T1Lib Support       |  enabled        |
+----------------------+-----------------+
|  GIF Read Support    |  enabled        |
+----------------------+-----------------+
|  GIF Create Support  |  enabled        |
+----------------------+-----------------+
|  JPG Support         |  enabled        |
+----------------------+-----------------+
|  PNG Support         |  enabled        |
+----------------------+-----------------+
|  WBMP Support        |  enabled        |
+----------------------+-----------------+

Does it say that JPG support is enabled there? Another way to check is to do something like:

<?php
var_dump(gd_info());
?> 

This is what phpinfo() is calling.

/me being the debian snob, says apt-get install debian

Aside from that, from what I could tell, you were doing things right...

Sorry I am not much more help.