V1.4.4 - Effect of changes in php.ini V1.4.4 - Effect of changes in php.ini
 

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

V1.4.4 - Effect of changes in php.ini

Started by borlavrin, April 19, 2006, 12:37:18 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

borlavrin

Question:
When changes are made in php.ini, are they picked up automatically by Coppermine or must it be re-installed first? In effect, is Coppermine 'reading' the new php parameters whenever the function is called?

The change has to do with uploading files > 2M.  Yes, I have picked the relevant info from the Trouble-shooting FAQ.

Situation:
On initial Coppermine installation, the php values were as in their default
Max_input_time = 60
Upload_max_filesize = 2M

I changed the php.ini to:
Max_input_time = 300
Upload_max_filesize = 8M

I also changed the Disk Quota in group control to 20,240 from 1024

Result:
I still seem to be bound by the 2M and 60 sec limit

I am stumped, need some guidance please.
Boris

Joachim Müller

coppermine doesn't read php.ini settings at all. They affect PHP. That's why the file is called php.ini. You have to restart your webserver to make them being taken into account. Make sure that you actually have the privileges to modify php.ini (usually you can only do so if the server is yours to administer). Run phpinfo.php to find out if they had an effect.
Think of coppermine as new stereo system in your car: charging your car's battery might have an impact on your ability to listen to music from your new stereo system. However, you can't ask your stereo's manufacturer on issues related to your car's battery.

borlavrin

Yes, phpinfo.php shows that the change was completed, and that is why I am stumped.  The server is on my own equipment and therefore I have full access.

Will have to seek further for the glitch.  Thanks for your clarification.

Cheers,
Boris

borlavrin

You were right GauGau, way down deep in the entrails of the server, there was a "Max POST Size" which had escaped my attention.  This upload issue can be marked as solved.

Cheers,
Boris