8MB upload limit - wierd!

[Artisan]

I'm using SnippetMasterPro v2.2.2 on a client's website, and despite having set up quite a few SMs now, I'm experiencing a persistent problem with this one. I can't get it to upload a file larger than 8MB.

The default server settings are as follows:
FTP file size limit: 100MB
PHP upload limit: 5MB
PHP timeout: 30 seconds

With the default settings above I couldn't upload anything larger than 2MB.

I placed a php.ini file in the public_html root containing the following:

Code:

upload_max_filesize = 20M
max_execution_time 240

(I've also tried a max_filesize of 40MB, but that makes no difference, the actual limit is still 8MB).

I have set " Limit File Size?" in Upload Group in SM to "No" (I also tried setting it to "Yes" and "20480" but it makes no difference).

I can upload a file that's 7.95MB, but not one that's 8.02MB, any idea what else I can try? Is there anything I should ask my hosting tech support? (if I just tell them there's a problem, they're likely to tell me that they don't support third party software!).

Any help would be appreciated.

Malcolm

[admin]

I think you should contact the hosting provider and ask them to increase the upload limit for your account.  It might be that they have restricted it in some other way then you have tried..

It's not really a question of supporting 3rd party software, as much as it is a question of configuration for PHP on your web server. 

You can tell them that Snippetmaster uses whatever PHP configuration is set up for the upload values in the php.ini file...  (In other words, there is nothing in snippetmaster that sets an upload size limit.)

[Jenkinhill]

I can upload a file that's 7.95MB, but not one that's 8.02MB, any idea what else I can try? Is there anything I should ask my hosting tech support?

The "standard" php.ini upload setting is for 8MB. If you can edit the server/site php.ini file to accept a larger value then that is the way to go ( you can often do this via the server file manager in ther host control panel). The variable to change is post_max_size.

Otherwise you will need to get the host to change it. Not allowing .htaccess over-ride of php.ini settings is quite commonly used to protect other users of a shared server who could have all their php resources hogged by another user, and also on servers using a jailed php setup.

[Artisan]

Thanks for the comments so far - I've got a support ticket running at the moment. So far, they've said "We keep a global php.ini and allow the creation of php.ini in web space on shared server accounts" and also "The logs indicate that the php.ini file isn't being read but a phpinfo() done on the script I've uploaded indicates it is". They're still looking into it.

Malcolm