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
These response values, deprecated in December 2015, will no longer be
returned in the response to action=login. This change should be deployed to
WMF wikis with 1.28.0-wmf.13, see
https://www.mediawiki.org/wiki/MediaWiki_1.28/Roadmap for the schedule.
Note that the lgtoken *parameter* to action=login is not removed, nor is
the 'token' response value included along with a NeedToken response.
This is expected to have a low client impact, since proper handling of the
Set-Cookie headers (rather than manually building cookies using these
response values) has been effectively required for some time now.
The original deprecation announcement is quoted below:
On Tue, Dec 15, 2015 at 11:11 AM, Brad Jorsch (Anomie) <
bjorsch(a)wikimedia.org> wrote:
> Long ago, the only mechanism for session management in MediaWiki was
> certain cookies set by the User class. When ApiLogin was written, in
> addition to setting these cookies as usual it also returned some of the
> values needed to construct these cookies on the client. Presumably this was
> to make things easier for clients that somehow couldn't handle the standard
> cookie headers.
>
> Then CentralAuth came along. Now, constructing the cookies manually would
> log you in to the local wiki only, without taking advantage of the SUL
> mechanism.
>
> Then T55032[1] happened, and clients that were using the
> manual-construction mechanism had to update their code because one of the
> cookie names changed and that wasn't part of the data being returned.
>
> And soon, we'll have SessionManager and AuthManager, which will make it
> possible for login to easily happen in ways that don't involve cookies at
> all.
>
> So it's time to eliminate the pretense that clients can manually construct
> the cookies instead of handing the standard HTTP cookie headers. Tentative
> plan is to deprecate them now and then remove them sometime during 1.28; if
> anyone objects to this schedule, please raise your concerns in
> https://phabricator.wikimedia.org/T121527.
>
>
> [1]: https://phabricator.wikimedia.org/T55032
>
> --
> Brad Jorsch (Anomie)
> Senior Software Engineer
> Wikimedia Foundation
>
--
Brad Jorsch (Anomie)
Senior Software Engineer
Wikimedia Foundation
The 'headitems' property for action=parse has been deprecated, and using it
will return a warning. If constructing a page from scratch, you should use
prop=headhtml instead. If updating an existing on-wiki page, use
prop=modules|jsconfigvars and load them into the existing ResourceLoader
code with mw.config.set() and mw.loader.using().
Also, the 'headitems' property will no longer return code related to
ResourceLoader. Loading ResourceLoader would require additional data that
is not sent by 'headitems', and given the deprecation it's not worth the
trouble to add that data.
--
Brad Jorsch (Anomie)
Senior Software Engineer
Wikimedia Foundation
We are going to finally switch off the deprecated domain rest.wikimedia.org
by September 1st. This should not affect any REST API users, as this domain
has been officially deprecated since January & sunset since April [1].
Since then, requests to that domain have returned an error informing users
about the move.
Access to the REST API is exclusively through the main project domains,
following the following pattern:
https://en.wikipedia.org/api/rest_v1/?doc
Thank you for your cooperation,
--
Gabriel Wicke
Principal Engineer, Wikimedia Foundation
[1]: https://lists.wikimedia.org/pipermail/wikitech-l/2016-April/085309.html