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
Hi,
The format of the version of MediaWiki releases to Wikimedia sites is
changing with the 1.27 release cycle.
Old format: 1.26wmf24
New format: 1.27.0-wmf.1
This affects the "generator" property of action=query&meta=siteinfo.
This is being done to bring the version numbers in compliance with the
semantic versioning standard[1]. See the Phabricator ticket for more
details[2]. This switch will happen with the 1.27.0-wmf.1 deployment,
which started today, and will reach all sites on Thursday, October 1.
Frameworks (like Pywikibot) that check the version number for
compatibility checking may need to be updated for the new format.
Apologies for the late notice.
[1] http://semver.org/
[2] https://phabricator.wikimedia.org/T67306
-- Legoktm
Apologies to those seeing this twice, but it's important enough to announce
widely.
---------- Forwarded message ----------
From: Matthew Flaschen <mflaschen(a)wikimedia.org>
Date: Tue, Sep 29, 2015 at 4:05 PM
Subject: [Mediawiki-api] Tips for using bots and user scripts with Flow
To: mediawiki-api(a)lists.wikimedia.org, EE List <ee(a)lists.wikimedia.org>
Flow will start appearing more widely soon when we release a feature to
allow users on certain wikis to opt into Flow on their user talk pages.
The most common thing you'll probably want to do on a Flow page is post a
new topic.
For Pywikibot, that is pretty easy, since they have Flow support now. See
https://www.mediawiki.org/wiki/Manual:Pywikibot/Flow .
For on-wiki scripts, you can use MessagePoster (you don't need to know if
it's a Flow board ahead of time!):
---
var title = new mw.Title( 'titleString' );
var posterPromise = mw.messagePoster.factory.create( title );
posterPromise.done( function ( poster ) {
poster.post( 'This is the topic title', 'This is the body
of a message posted with MessagePoster' );
} );
---
Depend on 'mediawiki.messagePoster' and 'mediawiki.Title'.
In some cases, you might want to check if a link is already there (e.g. to
see if a warning template already included links to a particular policy).
You can use prop=links for this.
Flow is based on an infinitely-scrollable list of topics, each of which is
its own page. So to use prop=links, you may need to loop through a set of
recent enough topics (e.g. 25) then combine them into a prop=links request,
e.g.
https://www.mediawiki.org/w/api.php?action=query&titles=Topic:Sojpiv245cuiw…
.
pywikibot has support for looping through topics.
Some bots need to check the header of a page for wikitext (e.g. a bot
exclusion template). This can be done with view-header, but I don't think
pywikibot has support for that yet (but it can be done directly). See
https://www.mediawiki.org/w/api.php?action=flow&format=jsonfm&page=Talk%3AF…
.
A better way to do this would be templatelinks, but I'm not sure if there
is an API to show templates PageX transcludes.
For other questions, contact us at #wikimedia-collaboration . Or, if a
certain tool needs Flow support and you're not sure where to start, you can
file a bug (you can also reply here, but a ping in IRC would be
appreciated).
Matt Flaschen