Printable View
Hey kids,
Right now if a video is over the alloted 100M for uploading and a person tries to upload a video larget than 100M, what's displayed is a server connection error, which doesn't help the unsuspecting user know that the file s/he's trying to upload has exceeded the allowed upload size.
How do I get it to return an error saying, "Sorry, the file you're trying to upload exceeds 100M" :?: Would that be some kind of .htaccess thingie :?:
See it
viewtopic.php?f=3&t=415
NO, no, that is not my issue. Trust me, I know how to get the files sizes allowed.
What I want is a page that displays an error saying that the file is too large when they try to upload a file larger than the alloted 100M (which is the limit for my sites, even though my host has 200M by default).
I only allow 100M sized videos on my site. Person tries to upload video 110M...they get "server connection error". It doesn't tell them that the file they tried to upload is too big. I need an error page telling them that they exceeded the file size upload...something along the lines of a file status...'We're sorry but your video file is too large, please reduce the size to 100M or less and try again"...something like that.
Open up your upload.tpl file and find the following code:
Remove one of the zeros at the end so that it looks like:Code:<input type="hidden" name="MAX_FILE_SIZE" value="1048576000">
I believe that this was supposed to be like the second one from the beginning, but someone may have fat-fingered the number (this is based on the fact that 100MB is the file size that is listed in the template by default). What this is intended to do is to pass a variable into PHP which tells PHP (from the browser side) what the maximum allowed file size should be. If a person attempts to upload a file bigger than this, you'll get a browser based error that the user can see before the upload even takes place. Without this (or in our case, this being incorrect), the file proceeds to upload until it hits the server's hard limit. When this happens, PHP refuses to accept anything further and a connection timeout is eventually displayed.Code:<input type="hidden" name="MAX_FILE_SIZE" value="104857600">
For your notes, the number is your maximum file size in bytes. The new number, 104857600, is 100MB in true bytes. The original number, 1048576000, is 1GB in true bytes. As originally written, you would never get an error until you upload a file bigger than 1GB, lol.
I have the 100M set in the .htaccess (my host doesn't use php.ini) and I noticed the number in the upload.tpl but didn't think much of it because of the .htaccess rule, but I'll see if this makes a difference and report back. Thanks!!
Just as I thought, that had absolutely no affect (since if it's doing this with a 173M file which is well under 1 gig...).
Here's what I did:
I have the upload on all my sites limited to 100M.
I just tried to upload a file that was 173M. When I hit the upload button, I got this error message:
Which is from the server. This just looks really bad. I was hoping that I could get a page that detects the size of the file a person is attempting to upload and display an error instead, like "sorry, that file is too big, try reducing the file size and uploading again blah blah blah".Quote:
Connection Interrupted
The connection to the server was reset while the page was loading.
The network link was interrupted while negotiating a connection. Please try again.
What I'm thinking is like with error documents, you can manipulate those with .htaccess..like instead of a person getting the dreaded "page not found" error, you can re-direct them to another page on your website like this:
Which would take the 404 error and make it go to your home page.
Side Note: This is also good for "hiding" affiliate links. ;)
LIke if your affiliate link is 6 miles long you could do this in .htaccess:
By making your affiliate link like this on your web page:
By removing the "zero" you are basically changing it from 1GB to 100MB. Which of your sites is doing this? That way, I can tell you whether or not you can manipulate the page with .htaccess or not.
It happens on all of my sites. Maybe I need to contact tech support at my host?
If you try to upload a file bigger than allowed on your site, do you get the connection error or do you see something saying" sorry the file is too big"?
One thing I did notice is this which is referencing the uu_upload.pl (don't know if this matters or not but this is the address that appears in the browser addy window):
I'm googling this now, it has to do with "file handler" or something... like it's not detecting that the file is too big and returning the person to a page telling them that the file is too big.Code:http://mydomainname.com/cgi-bin/uu_upload.pl?temp_sid=6b7a325c755c95c3b376c92abb088c46
Ahhhh.... well poo:
That's the problem right there. I didn't even notice that until you pointed it out. If you are using the upload progress bar, that script that your form is posting to is written in Perl, not PHP. Thus, the MAX_FILE_SIZE thing will not work (as that is a PHP function). I'll have to see if there is a workaround to this.
So if I disable the upload progress bar, I will get an error message instead of the server connection error? DANG! I like the little bar thingie! LOL
Ah ha!!! Found it!
Open up your uu_default_config.pm file (in your CGI-BIN) directory:
Change max_upload from 20971520000 (which is 20GB in true bytes) to 104857600 (which is 100MB in true bytes). If you attempt to upload something bigger than 100MB, the upload progress will display an error about the maximum file size being exceeded.
Oh poo...that wasn't it either.
I put in a support ticket to my web host, they're checking on it.Quote:
Connection Interrupted
The connection to the server was reset while the page was loading.
The network link was interrupted while negotiating a connection. Please try again.
Which site of yours did you change? You should have gotten an error about the file being too large immediately after hitting upload. I'll post a screenshot.
http://www.bootyplex.com/templates/i...screenshot.jpg
POOOOOOO I'm not getting that error. :( I get the same server error on all my vShare sites. I changed the UU file on all my sites just to see and still get that error.
Try it on rappelzvideos.com
That's really weird?!? The files in your CGI-BIN are CHMOD 755 correct? Also, could you display what is listed in your uu_default_config.pm?
Oh yeah, everything is 755..been using vShare since 2.4...the only thing I changed is the regular settings.
Here's my uu file
Code:package uu_default_config;
use strict;
use Exporter;
@uu_default_config::ISA = qw( Exporter );
@uu_default_config::EXPORT = qw($config);
use vars qw($config);
use vars qw($base_dir);
$base_dir = '/home/*****/public_html/rappelzvideos';
$config = {
config_file_name => 'uu_default_config',
temp_dir => $base_dir . '/templates_c/',
upload_dir => $base_dir . '/video/',
unique_upload_dir => 0,
unique_upload_dir_length => 16,
unique_file_name => 0,
unique_file_name_length => 16,
max_upload => 104857600,
overwrite_existing_files => 0,
redirect_after_upload => 1,
param_dir => $base_dir . '/templates_c/',
pass_param_dir => 1,
redirect_url => 'http://rappelzvideos.com/upload.php',
redirect_using_js_html => 1,
redirect_using_html => 0,
redirect_using_js => 0,
redirect_using_location => 0,
get_data_speed => 1000,
disallow_extensions => '(sh|php|php3|php4|php5|py|shtml|phtml|cgi|pl|plx|mp3|exe|scr|htaccess|htpasswd)',
allow_extensions => '(3gp|mp4|mov|asf|avi|flv|wmv|mpg|mpeg|mpeg4|xvid|divx|3gpp)',
normalize_file_names => 1,
normalize_file_delimiter => '_',
normalize_file_length => 32,
link_to_upload => 0,
path_to_upload => 'http://'. $ENV{'SERVER_NAME'} . '/uploads/',
send_email_on_upload => 0,
html_email_support => 0,
link_to_upload_in_email => 0,
email_subject => 'Uber File Upload',
to_email_address => '[email protected],[email protected]',
from_email_address => '[email protected]',
log_uploads => 0,
log_params => 0,
log_dir => $base_dir . '/templates_c/',
};
1;
This is looking as though it is going to be an issue on your particular host, so it may be best to keep that ticket you have open. What is happening is that when you post a file bigger than the maximum file size, you are supposed to get an error message about the file size being exceeded. However, what you are getting is a server connection failure. You may not have the permissions (on your server) to set the CGI POST_MAX size.