Cannot batch add large images (small are OK)

[clocktowerweb]

Hi 

Firstly, I have searched this forum loads but cannot find another person with the same problem as me.

I can upload files OK (either with FTP or through a browser).  All album permissions are 777.

Problem comes when you do a "Batch add files".

Small files are fine and work well.  Large files show up on the Batch add files page as a broken image and won't batch add.

See attached screen shot showing the problem:  The top file I am trying to batch add is around 900k.  The bottom file is around 24k.  I am not sure at what size it flips from OK to not OK.

BTW, when you go to upload an image the system states "Maximum allowed file size is 2000 KB" so it's not that I am trying to add pics that are too large.

As requested I have set up a test user on the site:
http://66.235.160.105/
user test
pass test
and I have set the system to print diagnostics and to single uploads.

No doubt you will need more info - let me know and I will sort it.

Many thanks for any help!

Paul

[Joachim Müller]

there are server-sided restrictions that will keep you from uploading large files (both in file size and dimensions), see http://forum.coppermine-gallery.net/index.php?topic=24088.0, no matter what you specify in coppermine's config.
There are tons of postings where people say that they can upload small files just fine, but fail to upload larger files, you haven't searched thoroughly.

[clocktowerweb]

Hi GauGau

Thanks for the reply.  I have checked all the PHP variables referred to on the page you linked to.  All the settings on the server are the defaults shown.  The images do appear to upload correctly; it is the batch add process that fails.

In the screen shot I posted, the URL to the upper (large) broken image is:

http://66.235.160.105/showthumb.php?picfile=product_pics%2FDSCF3479.JPG&size=48

Something (GD2 I guess because that is what Coppermine is configured to) is not successfully displaying this as a thumbnail.

The URL for the lower (small) image which displays fine is:

http://66.235.160.105/showthumb.php?picfile=product_pics%2Fwebcam.jpg&size=48

I know the upload process worked OK because I can download the large image:

http://66.235.160.105/albums/product_pics/DSCF3479.JPG
Size: 921k and 2272 x 1704 px

When I batch add this file the thumbnail is shown as a broken image both before and after I hit the "Insert selected files" button.

I have installed Coppermine on other servers without any problems.

And I have now found a suitable thread that pretty much matches my problem:
http://forum.coppermine-gallery.net/index.php?topic=24974.0
The suggestion there is that GD2 is running out of memory and to install ImageMagik which I will do and report back here.

Thanks again

Paul

[Nibbler]

You will certainly need more than the 8M default memory limit to be able to resize that pic using GD. IM should work.

[clocktowerweb]

Thanks Nibbler.

I logged in via telnet and ran 'whereis convert' - it showed a the program in /usr/bin/ so I have put that path in the config section of Coppermine and set the Method for resizing images to Image Magick.

However when uploading I am now getting this error:

The file 'albums/userpics/DSCF3586.JPG' can't be inserted in the album
Error executing ImageMagick - Return value: 127
Cmd line :
/usr/bin/convert -quality 100 -antialias -geometry 100x75 'albums/userpics/DSCF3586.JPG' 'albums/userpics/thumb_DSCF3586.JPG'
The convert program said:
File: /home/virtual/site6/fst/var/www/html/db_input.php - Line: 391

Yes, I have searched this forum for 'Error executing ImageMagick - Return value: 127' and seen lots of threads, most say that IM is not installed (it is) or that the path is wrong (it isn't).

The file /usr/bin/convert has permissions 755.

Yet if I run the command ('/usr/bin/convert -quality 100 -antialias -geometry 100x75 'albums.......') in the telnet command line it works perfectly and creates the thumbnails.

Seems to be a permissions issue then?

Grateful for any help! 

Paul

[Joachim Müller]

yes, should be a permission issue - ask your webhost for support.