I want people to be able to upload very large zip files, say possibly 100-200MB through the Webform module, after submitting some basic contact info. Anyone see a problem with this, as far as all the post info being lost if it should fail?

I don't imagine more than 1 person a day would be doing this. And that's extremely optimistic. The product is uploading a batch of zipped images, which i do processing work on etc..

Or should I forget about doing this on my own site and go with a cheap upload service site?

Comments

throk’s picture

Good question.
The usual PHP file upload limit is like 4mbs. Depending on your hosting provider you can change that or even us a hack in the .htaccess file. But most hosting providers prohibit this. Some will shutdown your account if they find you doing this!

That being said, uploading large content through an HTTP isn't the most stable thing. Especially if you have to use a hack to get it to work. So yeah, use a free upload site like: http://fileurls.com/ (it's free)
__________________________________________________________
work in progress www.TheHappyHourHero.com

aterchin’s picture

Yeah, i'm usually wary of changing too many of the default php.ini settings other than the ones drupal requires for usability. theres the post max fillesize, the memory limit. ugh. i just don't want my scripts to get lost somewhere and people getting too frustrated and going away.

That one u linked to looks great. Just have to give the customer idiot proof instructions to copying the url to my site. maybe i'll see if i can make the whole site open up in greybox on my site. another idea.
Sounds like a good plan. i'll have to test it out with a big file.

aterchin’s picture

OR...does anyone know a good reliable upload service with a decent price?

ceejayoz’s picture

You could probably find or write a little app that uses Amazon.com's S3 (Simple Storage Service). It's $0.10 per gigabyte per month for storage, an $0.15 per gigabyte for transfer. Very reasonable.

aterchin’s picture

thanks! ill definitely look into that. yeah, even if another mass storage site like that fileurls one linked to above goes down, the fact that it's amazon leads me to believe..well, that they'll be around for a while :) and it's a back up plan.

i may start using fileurls for now. got it popped up in a link using greybox. unfortunately a person will have to copy the link after their file uploads into the webform for submission. if i can automatically get amazon to link the download to an email, then a customer who's submitting the file to me won't even have to wait and go through the extra step to copy and paste the URL into my webform's textfield before they submit to me. i'm just thinking out loud here. thanks for the advice.
adam

blueflowers’s picture

seems it would be a lot easier to just change the 2 values in a php.ini file, no?

You seem to be jumping through a lot of hoops to get this going when it's as simple as doing the following:

create a file called php.ini and put the following inside:

upload_max_filesize = 120M
post_max_size = 240M

upload said file to your server and drop it in the root of your drupal installation.

Your clients should now be able to upload files of 120M or less.

Fourth Wall Media
Toronto, Canada

aterchin’s picture

True. I was just unsure if there were any implications of large file sizes timing out unexpectedly, especially if the upload form was tied into a webform (using POST values and whatnot, such as user info, address, contact, etc..) and then would i lose that information as well. I've had experiences with large uploads timing out on sites where i've been a user and lost all the POST info i've submitted and just looking to avoid that sort of thing on my site. But my experience level with this isn't great so i was inclined to ask just incase. still don't have a solid answer to this but i worked out my problem for now.

shedevches’s picture

Hooray! Thank you !

Man.. I can't believe how much time I wasted looking for this.. thank you thank you..

aterchin’s picture

as a sidenote for bluehost: if you don't see the changes you make in php.ini reflected on your site you need to run a script that copies php.ini into EVERY folder in your drupal install in order to see the changes you make in the main php.ini file in your root directory. search their support for "php.ini".

dman’s picture

That sounds a bit mad.
It may be that it has to be relative to the running script - but because index.php is the only running script in Drupal then the root is the only place.

Other normal php-page written sites may require this or something (it still sounds a bit demented) but I don't think that scattering copies throughout a Drupal distro can be a good thing.

.dan.
How to troubleshoot Drupal | http://www.coders.co.nz/

kevinquillen’s picture

You wouldn't want the form to accept over 20 MB... any number of factors could affect the upload process like connectivity, server drop, browser freeze... very frustrating for the user and they won't attempt to try more than one or two times with a huge file.

But yeah, anything higher than the default is set in Drupal settings, and beyond that, php.ini.

===========
read my thoughts