| commit | 40e18e45343ca4d1366837c2f55be63d7bf4f7d2 | |
| author | Timo Tijhof <krinklemail@gmail.com> | |
| Tue, 4 Jun 2013 23:02:10 +0000 (5 01:02 +0200) | ||
| committer | Timo Tijhof <krinklemail@gmail.com> | |
| Wed, 5 Jun 2013 14:07:17 +0000 (5 16:07 +0200) | ||
| tree | 5d10bdf3dabed84edaffa6ce92c814aa4d04bb1e | treesnapshot (tar.gz zip) |
| parent | 58f71c7e9eca460bfaf518c6c1fecaca87b58dd3 | commitdiff |
Installer: Remove wgResourceLoaderMaxQueryLength in LocalSettings
This can change from one web server to another. Hardcoding it
in LocalSettings is unnececary (and could even cause problems
when a MediaWiki install is moved to a server with a lower
limit than the original server, as ResourceLoader would still
be acting on the old limit).
Similar to how wgUsePathInfo is currently dynamically set.
The less cruft in LocalSettings by default the better imho.
Except for stuff that makes sense to be sticky, explicit and
cached. Or stuff that is every commonly enabled and is therefor
convinient (such as wgEnableUploads/wgUseInstantCommons).
Change-Id: I58cb185f8dc1650a76c60c7fd04767fb74b32be2
This can change from one web server to another. Hardcoding it
in LocalSettings is unnececary (and could even cause problems
when a MediaWiki install is moved to a server with a lower
limit than the original server, as ResourceLoader would still
be acting on the old limit).
Similar to how wgUsePathInfo is currently dynamically set.
The less cruft in LocalSettings by default the better imho.
Except for stuff that makes sense to be sticky, explicit and
cached. Or stuff that is every commonly enabled and is therefor
convinient (such as wgEnableUploads/wgUseInstantCommons).
Change-Id: I58cb185f8dc1650a76c60c7fd04767fb74b32be2