When list=allusers is used with auactiveusers, a property 'recenteditcount'
is returned in the result. In bug 67301[1] it was pointed out that this
property is including various other logged actions, and so should really be
named something like "recentactions".
Gerrit change 130093,[2] merged today, adds the "recentactions" result
property. "recenteditcount" is also returned for backwards compatability,
but will be removed at some point during the MediaWiki 1.25 development
cycle.
Any clients using this property should be updated to use the new property
name. The new property will be available on WMF wikis with 1.24wmf12, see
https://www.mediawiki.org/wiki/MediaWiki_1.24/Roadmap for the schedule.
[1]: https://bugzilla.wikimedia.org/show_bug.cgi?id=67301
[2]: https://gerrit.wikimedia.org/r/#/c/130093/
--
Brad Jorsch (Anomie)
Software Engineer
Wikimedia Foundation
To operate correctly, action=purge needs to write to the database, which
means it should be done using a POST rather than a GET request.
As of Gerrit change 310560,[1] action=purge will begin emitting a warning
when used via GET. This should be deployed to WMF wikis with 1.28.0-wmf.20,
see https://www.mediawiki.org/wiki/MediaWiki_1.28/Roadmap for the schedule.
Clients that use action=paraminfo to determine whether to use GET or POST
for an action should automatically switch to POST; any others should
manually switch to using POST for this action as soon as possible.
To check if your client's user agent is detected making such submissions,
you can also use ApiFeatureUsage[2] and look for 'purge-via-GET' once
1.28.0-wmf.20 is rolled out to wikis your client is using.
It is planned that this warning will be changed to an error during 1.29.
Let's avoid having a repeat of T142155,[3] update your code ASAP instead of
waiting until it breaks. Thanks.
[1]: https://gerrit.wikimedia.org/r/#/c/310560/
[2]: https://meta.wikimedia.org/wiki/Special:ApiFeatureUsage
[3]: https://phabricator.wikimedia.org/T142155
--
Brad Jorsch (Anomie)
Senior Software Engineer
Wikimedia Foundation
With formatversion=1, boolean response fields are typically returned as the
empty string when true and are absent from the response when false. With
formatversion=2, boolean response fields in JSON and PHP formats are
supposed to be returned as native boolean true when true, and either native
boolean false or absent from the response when false.
Any boolean response fields that use the formatversion=1 semantics with
formatversion=2 should be fixed. Please file tasks in Phabricator if you
encounter such fields.[1] Clients using formatversion=2 should be prepared
for such response fields to be fixed without further warning.
[1]:
https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?tag=MediaWiki…
--
Brad Jorsch (Anomie)
Senior Software Engineer
Wikimedia Foundation
With the merge of Gerrit change 321406,[1] come some breaking changes to
the formatting of errors and warnings from some modules. These changes
should be on Beta Labs shortly, and should be deployed to WMF wikis with
1.29.0-wmf.6.
- Error codes returned by some modules have changed. Notably, codes from
query submodules will no longer include the module prefix, e.g. if you
supply a bad continuation parameter for prop=revisions it will report error
code 'badcontinue' instead of 'rvbadcontinue'. Other codes may have changed
as well, e.g. for list=allpages the error for attempting to use redirects=1
in generator mode is now 'invalidparammix' instead of 'params'.
- If you're attempting to parse the human-readable 'info' text of
errors, that text may have changed. Use cases should be submitted in
Phabricator[2] as feature requests to include the needed data in a
machine-readable format alongside the error message.
- action=emailuser may return a "Warnings" status, and now returns
'warnings' and 'errors' subelements (as applicable) instead of 'message'.
- action=imagerotate returns an 'errors' subelement rather than
'errormessage'.
- action=move now reports errors when moving the talk page as an array
under key 'talkmove-errors', rather than using 'talkmove-error-code' and
'talkmove-error-info'. The format for subpage move errors has also changed.
- action=rollback no longer returns a "messageHtml" property on errors.
Use errorformat=html if you're wanting HTML formatting of messages.
- action=upload now reports optional stash failures as an array under
key 'stasherrors' rather than a 'stashfailed' text string.
- action=watch reports 'errors' and 'warnings' instead of a single
'error'
This same change brings the ability to request errors and warnings in
languages other than English and formats other than plain text. See the new
'errorformat', 'errorlang', and 'errorsuselocal' parameters to the 'main'
module.
[1]: https://gerrit.wikimedia.org/r/#/c/321406/
[2]:
https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?tag=MediaWiki…
--
Brad Jorsch (Anomie)
Senior Software Engineer
Wikimedia Foundation