batch upload problem: exhausted memory, .htaccess method doesnt work batch upload problem: exhausted memory, .htaccess method doesnt work
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

batch upload problem: exhausted memory, .htaccess method doesnt work

Started by voydd, October 25, 2007, 02:08:21 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

voydd

Hi there.
First of all, here is my gallery:
http://voydd.pl/cpg1413/index.php
U may log as "new", password "test".
But as long as problem concerns batch upload not http, I think there is no need fot U to do so.
Problem emmerges when I try to upload files with hi-res (calculating needed memory it is like 12M ish). I read Your sticky topic, many soved treads about batch-upload problems and contacted my webhost asking about changes in php.ini. They replied me suggestin' usin' .htaccess file. So I created one and put such a line inside:
php_value memory_limit 20M
As long as I dont know where to place the .htaccess file, I copied it to albums and main cpg1413 folder. And still it didnt work. Then I read about changing files index.php and install.php by placing there on a top a line:
ini_set("memory_limit","32M");
That didnt change anything neither.
I have to say that uploading files corresponding to 8M or less works perfectly.
I hope that there is a diffrent sollution fot this case than making files smaller.
voydd

Sami

Do as suggested by your hosting and then check your phpinfo() and see if your memory limit takes the effect or not
if it doesn't work then ask your host for support
‍I don't answer to PM with support question
Please post your issue to related board

voydd

Thanks for the advice about phpinfo(). Its really powerful diagnostic thing:)
In my case I just had to put more memory in .htaccess file...
Problem solved