Override php.ini settings

Posted: Fri Feb 10, 2012 2:49 pm

I'm having difficulty overriding my php.ini settings on my dev server.

Setup:

Ubuntu Server 10.xx LTS
PHP 5.3.2
Apache 2

Specifically I'm trying to override the max_upload_filesize and post_max_size settings. I've read around the net and it seems every "claims" it can be overridden with something like...

Code:

<IfModule mod_php5.c>


php_value upload_max_filesize 100M


php_value post_max_size 100M


<IfModule>

in the .htaccess file. I've tried it in the module root folder... as well as the root .htaccess.

This seems to have no effect on the server though. Anyone have any other thought tips or suggestions??

Note** I have access to change it via the php.ini... but not every has that access on their server and I'm looking for an alternate method to change the settings if possible.

Worker Joined: Mar 30, 2009 Posts: 132

i think most pay hosts has the ability to change some php.ini settings

I had to make some mods to mine where I am at. i believe it got saved in /cgi-bin/ as php.ini

might want to try that

Posted: Sat Feb 11, 2012 4:27 pm

kd8hho, Thanks for the attempted answer, however, I'm running my own server and an issue I ran up against is the max sizes in the php.ini settings. I have full control of the server and can edit it to be w/e I want... hence the...

Quote:

Note** I have access to change it via the php.ini... but not every has that access on their server and I'm looking for an alternate method to change the settings if possible.

note I put at the end. The idea is to have a fallback method in place in the instance the user does NOT have the ability to change php.ini settings.

registered · Posted: Sat Feb 11, 2012 8:41 pm

killing-hours,

Since you know what version of PHP you're running locally, have you tried taking out the first and last lines? Just curious...

Also, have you tried a script with just phpinfo() in it placed in the same directory as your .htaccess and checked the settings? Something tells me you have to have the overriding .htaccess file in the directory where the core script is at. For example, I used to use Gallery long back and, of course, it had need for a much larger upload size. It also was integrated with *nuke in such a way that it wasn't called through modules.php, but rather directly. So, I had to place a separate .htaccess in the directory of the "controller" script for Gallery and then it picked it up.

Just wondering if this might be where you are having issues.

Posted: Sun Feb 12, 2012 9:35 pm

montego,

The idea was to have an override in place packaged with the module to set a higher limit on some settings. On my server I didn't have "Allowoverrides All" enabled in the httpd.conf (and still don't) so that was the cause.

This raised an issue though... if the end user has no idea about allowoverrides or doesn't have it turned on in their shared server then the upload would silently fail.

The solution I think I'm going to land on is checking the information and raising attention to it so the user will be aware of the limitations of of the environment as well as provide links on how to change it if they can.