Note that there are some explanatory texts on larger screens.

plurals
  1. POTrying to upload video file in php, but it's too large
    primarykey
    data
    text
    <p>I'm trying to use a html file input tag to upload videos to a php 5.3.10 script running on a wamp 2.2 server. I found that it won't upload and apparently it is too big. </p> <p>I have gone into php.ini and changed the following to 100M: post_max_size, upload_max_filesize</p> <p>and memory_limit is at 128 MB. I restarted WAMP and tried to upload the file, but it still did not upload. I then cleared my cache and history and restarted wamp, and it still didn't work. I then cleared the cache, turned off wamp, turned off my computer and then started up again, started wamp, and it still didn't work.</p> <p>The video I am trying to upload is about 25 MB.</p> <p>Inspite of the changes I made in php.ini, the Apache Error Log keeps posting this error, everytime I try to upload this video:</p> <p>[error] [client 127.0.0.1] PHP Warning: POST Content-Length of 26246222 bytes exceeds the limit of 8388608 bytes in Unknown on line 0, referer: <a href="http://localhost/uploadFile.html" rel="nofollow">http://localhost/uploadFile.html</a></p> <p>Also a php script with the following line:</p> <p>echo ini_get('upload_max_filesize'), ", " , ini_get('post_max_size'), ", ", ini_get('memory_limit'): prints out: 100M, 8M, 128M</p> <p>So it seems that it is the post_max_size that is the problem, eventhough I set to 100M in php.ini</p> <p>What could be the problem? How do I solve this?...</p> <p>Here is a link to the contents of my php.ini file, which is under C:\wamp\bin\php\php5.3.10:</p> <p><a href="http://pastebin.com/RUVE093u" rel="nofollow">http://pastebin.com/RUVE093u</a></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload