| commit | 13155a331795eab2a50a3f92f81d4e7b53ea3760 | |
| author | Florian <florian.schmidt.stargatewissen@gmail.com> | |
| Sat, 25 Jun 2016 16:43:23 +0000 (25 18:43 +0200) | ||
| committer | Florian <florian.schmidt.stargatewissen@gmail.com> | |
| Mon, 27 Jun 2016 14:50:25 +0000 (27 16:50 +0200) | ||
| tree | 34caaf512070aa5a584e7929bcddc8e3f9d19d10 | treesnapshot (tar.gz zip) |
| parent | 4d8738f6e6be98fc8cab79555e987cf468756faf | commitdiff |
Expose $wgMaxArticleSize in siteinfo query api
Currently, an user of the api has to try to save a page to see,
if it's too big, or not. A much saner way would be, that the api user
reads the siteinfo of the target wiki to know the maximum size of a
page and trim the edit to not exceed this limit.
This commit exposes the value of the configuration variable, which
handles the maximum article size.
Bug: T138669
Change-Id: I25a4c1b9013f98e5b0a263a637c8b006dccfd5ad
Currently, an user of the api has to try to save a page to see,
if it's too big, or not. A much saner way would be, that the api user
reads the siteinfo of the target wiki to know the maximum size of a
page and trim the edit to not exceed this limit.
This commit exposes the value of the configuration variable, which
handles the maximum article size.
Bug: T138669
Change-Id: I25a4c1b9013f98e5b0a263a637c8b006dccfd5ad
| includes/api/ApiQuerySiteinfo.php | diffblobblamehistory |