By tdellaringa on

Hi folks,

Having real trouble getting past the 2MB limit with the audio module. I modified my .htaccess like so:

# bump up upload limit for audio files
php_value upload_max_filesize 30M
php_value post_max_size 30M

On the audio settings page, it tells me I can upload files up to 15MB (apparently MediaTemple has certain limits which cannot be passed - but 15 meg would be fine).

Problem is, on the actual create audio content page, it still says I have a 2MB limit, and won't let me upload anything bigger.

I do have access to a php.ini file, but when I tried to change that I got all kinds of fatal memory errors, so I set it back and figured I'd use the .htaccess. Does anyone know how to fix this or have any suggestions?

Thanks

Tom

Comments

devx’s picture

devx commented

just finished posting this so try it: http://drupal.org/node/127417

basically if the .htaccess php_value doesnt work, try the php.ini in site root(different from the main php.ini)

tdellaringa’s picture

tdellaringa commented

Thanks, none of this seems to be working - all I get from phpinfo() is 2MB whether I try ini or htaccess. MT gives you an 'etc' directory at the root where you put your custom ini, but it doesn't seem to work. I'll contact them.

Anyone else at MT have this issue?

devx’s picture

devx commented

my experience(1&1) with custom php.ini is that its only available from the directory you place it in. eg: public_html/blah/php.ini in this case the settings you have defined are only accessible to the "blah" folder....so you'll get different readings from a phpinfo file in public_html/info.php vs public_html/blah/info.php

could be just that this is a particular setting that cannot be modified as per MT's AUP?

tdellaringa’s picture

tdellaringa commented

According to MT, and I have been going round and round with them on this now for days, is that the php.ini file in the directory they specify will affect all domains and folders. Indeed when I run php_info() the limit is bumped up. Problem is I'm getting these fatal memory errors now. On this, they claim

Some customers have reported running into this problem when using scripts that dynamically resize large images into smaller versions. Low-loss image resizing is an extremely memory hungry process so running into this error is very likely. A work-around is to pre-process the images and store them in another location or cache; or you can call on another script written in a language that does not have this memory limit problem (like perl) to do the actual processing.

You can also add an .htaccess file with the following command in it to increase the php_memory_limit:

php_value memory_limit 16M

I tried this and it doesn't help, still getting fatal memory errors. Then they tell me "hey, upgrade your service to a dedicated server for $50/month and it will work fine!" Sure it will, and like I want to do that.

Am I the only one having this problem? I don't see any trace of this issue on the audio module page.

Rob_Feature’s picture

Rob_Feature commented

Same problem here on MT....I have a friend who made it work, so I'm just waiting to hear how he did it...

-Bob Christenson
Owner/Designer, Mustardseed Media, Inc.
MustardseedMedia.com

/**
  * Bob Christenson
  * Mustardseed Media
  * http://mustardseedmedia.com
  */
Rob_Feature’s picture

Rob_Feature commented

Ok, I got the solution:

The default media temple php.ini file uses the "#" character as their comment. This is incorrect. It should be ";". Replace all the # with ; and it should work for you....

-Bob Christenson
Owner/Designer, Mustardseed Media, Inc.
MustardseedMedia.com

/**
  * Bob Christenson
  * Mustardseed Media
  * http://mustardseedmedia.com
  */