Errors uploading large image files

[asabet]

Prior to a recent server change, our members could upload large (up to 16MB files) to our Photopost Pro galleries at SeriousCompacts.com and Mu-43.com - Micro Four Thirds User Group

These large file uploads no longer work. I was getting a generic "image(s) too large" white page error and then remembered that on the old server I had to modify the .htaccess to include the following:

#set php max upload size in MB
php_value upload_max_filesize 20M
#set max post size
php_value post_max_size 20M

#set max time script can take
php_value max_execution_time 200
#set max time for input to be recieved
php_value max_input_time 200

In the process of moving the new server, someone had commented out these lines. When I restored them and try the large file upload, I get the following error:

"Fatal error: Allowed memory size of 50331648 bytes exhausted (tried to allocate 19712 bytes) in /home/asabet/public_html/seriouscompacts.com/gallery/image-inc.php on line 116"


I contacted URLJet about this issue, and they responded that "php limits have been increased" and that the uploads should now work. However, with my test image (http://farm6.static.flickr.com/5064/...24a4fd49_o.jpg) I again got:

Fatal error: Allowed memory size of 50331648 bytes exhausted (tried to allocate 19712 bytes) in /home/asabet/public_html/seriouscompacts.com/gallery/image-inc.php on line 116


Contacted URLJet support again and got the following response:

Amin,

The limits on the server are more than adequate to upload the image your referring to.

The issue is in the gallery program itself.
Fatal error: Allowed memory size of 50331648 bytes exhausted (tried to allocate 19712 bytes) in /home/asabet/public_html/seriouscompacts.com/gallery/image-inc.php on line 116

gallery/image-inc.php on line 116.... refers to a hard limit in the gallery's php settings, not the server. The part I wonder about is that the program need over 50mb to upload an 8.5mb image?

I explained to them that this software was working perfectly fine for us prior to the server change but was wondering whether you could help me with this.

As I said in another post, the new server removed support for exec in case that makes any difference here. We've been using GD2 all along.

Thanks,
Amin

[Chuck S]

Amin it comes down to the processor your using.

It is quite common to see issues like this with GD2 and there are plenty of examples here. You can raise your PHP memory_limit to say 72MB.

However if your going to use GD2 as your image processor there is no way to upload huge images. GD2 will simply not process huge images since it is part of PHP. If you want to process huge images you need to use Imagemagick and that means your host needs to enable EXEC.

[asabet]

The strange thing is that I was using GD2 even before the change to a newer server with the same host, and it worked fine back then .

[Chuck S]

well you where using Imagemagick from what you told us as your previous threads dealt with disabling of exec.

Anyway I seriously doubt you where using GD2 to process images over 2-3mb. It just doesnt work since it requires too much memory from PHP and causes PHP to crash. Its very common a problem and nothing we can do in our program.

You can make sure under admin => upload options makes sure your image max width and height are no more than 1200 and your quality is around 70 or 80 but aside from that your only going to be able to process what your server's image processor lets you based on your server restrictions.

[asabet]

Chuck, I'm pretty sure I was using GD2 all along with Photopost. My previous threads had to do with EXIF extraction not working due to getting rid of exec and also with ReviewPost issues after switching from ImageMagick to GD2.

At any rate, I guess I'm now stuck and will make the changes to the upload settings.

[Chuck S]

Yeah its pretty cut and try GD2 only handles smaller images as it is tightly constained by PHP restrictions being part of PHP.