Joomla lets you impose an artificial limit to the upload size that works independently of the php settings. Which is to say that:
K2 has to work within the php settings, so all joomla can do is limit the size of an upload to be less than what php would otherwise allow. The way it does this is brain dead and quite annoying -- it waits until the entire upload is complete and then disallows it at the last instance after the entire file has been sent.
Truthfully, this is one of the weaknesses of php's underlying functions, the way HTTP posts work, and the way media manager works in joomla. Media manager is one of joomla's weaknesses and could really use an extensive overhaul.
FTP as an alternative has the issues of lack of integration, where people can easily misplace an asset, and can also require that you 777 all your directories, opening up security holes on shared hosts (although most shared hosts now utilize fastcgi to mitigate these issues and run apache as the user).
Another alternative was the flash upload module, but unfortunately recent changes to flash5 have rendered most of those widgets broken, since adobe has made it so that flash can no longer have its local file manager opened through a javascript event.
There will never be a browser based solution that works for all people on all hosts with all configurations, and joomla has taken the same approach that many projects have taken, and provided a simple lowest common denominator solution.
Carolyn Harris said:I have increased the max_upload_size and memory_limit AND renamed php.ini to php5.ini and I STILL see within the admin when making a new K2 entry "Max upload size 400M" even though I put a much higher file size limit in the php.ini (now php5.ini) file.
Why does K2 not recognize this?