|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2010-10-04 13:39 UTC] cataphract@php.net
-Status: Open
+Status: Wont fix
[2010-10-04 13:39 UTC] cataphract@php.net
|
|||||||||||||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Sun Oct 26 02:00:01 2025 UTC |
Description: ------------ Issue #50684 ("max_file_uploads can't be changed from .htaccess (or ini_set)") is currently "closed", but was not satisfactorily resolved. "jani@php.net" did not provide a legitimate reason why the "max_file_uploads" setting should not be override-able at the apache or .htaccess level. Since PHP allows other settings like "memory_limit", "max_execution_time", and the like to be overridden, it does not make intuitive sense for the "max_file_uploads" setting to be left out. Until this is fixed, we are running with this setting disabled. Meanwhile, other developers who have encountered this "feature" of PHP 5.2.12 and later have had to resort to ugly, non-standard JavaScript hacks to get around the inherent problems with the approach of this setting. See: http://allinthehead.com/retro/349/the-curse-of-max_file_uploads I would dearly like to see this setting not go the way of the ill-fated "safe_mode" setting, where it's implemented but no one can use it because it isn't useful to anyone in particular.