When list=allusers is used with auactiveusers, a property 'recenteditcount'
is returned in the result. In bug 67301 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, 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
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.
Brad Jorsch (Anomie)
Mediawiki-api-announce mailing list
TL;DR: I'm proposing deprecating a bunch of parameters. See
In the action API, there are two ways to parse a page/revision: using
action=parse, or using the rvparse parameter to action=query&prop=revisions.
Similarly, there are two ways to get a diff: using action=compare, or using
parameters such as rvdiffto to action=query&prop=revisions. And then
there's action=expandtemplates versus the rvexpandtemplates parameter to
prop=revisions. This is a somewhat annoying bit of code duplication.
Further, the prop=revisions versions of these features have somewhat
strange behavior. rvparse forces rvlimit=1. rvdiffto and related parameters
will sometimes output "notcached" with no way to directly handle the
So, I propose deprecating all of these parameters. The parameters that
would be deprecated are the 'rvdifftotext', 'rvdifftotextpst', 'rvdiffto',
'rvexpandtemplates', 'rvgeneratexml', 'rvparse', and 'rvprop=parsetree'
parameters to prop=revisions, and the similarly named parameters to
prop=deletedrevisions, list=allrevisions, and list=alldeletedrevisions.
Following the normal action API deprecation policy, they'd output warnings
but would continue to function until usage drops sufficiently or until it
becomes too much trouble to fix them, and they wouldn't receive new feature
If anyone would object to this plan, please reply at
https://phabricator.wikimedia.org/T164106, or here if you really hate
Phabricator. If there aren't major objections, I'll probably do the
deprecation in the next week or two. Thanks.
Brad Jorsch (Anomie)
Senior Software Engineer
-----BEGIN PGP SIGNED MESSAGE-----
I need an API request which lists of user names of all users who did an
edit (or upload) within the last 6 months.
Is that somehow possible? Sadly the "Active Users" do not provide a
possibility for a range / starting date. Or is this a configuration
within the LocalSettings?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----
Hello. I am writing a crawler and a parser to obtain structured information
from Wiktionary pages
However, i saw that a site called as yourdictionary already have structured
information from Wiktionary
So i wonder, are there any APIetc that does provide structured information?
Or they have written their own custom crawler and parser?
page : https://en.wiktionary.org/wiki/game
some structured information from yourdictionary . com
So i dont want to waste my time if any easier way to obtain in such time
because i believe i will be writing a lot of cases
To sum up, my question is, are there any way to obtain machine readable
format of pages?
Or i have code my own custom parser?
Dear list members,
yesterday I fiddled around with my MW-API (v1.27.2) and a registered
bot-user (Special:BotPassword) using the Httpful PHP client library .
My goal is to edit and create pages with my bot.
Making GET queries is working very well but I can’t login. − So I need
some advices from you, please.
Like I understood I have to make 4 requests:
1. = GET to "api.php?action=query&meta=tokens&type=login"
2. = POST to "api.php?action=login".
3. = POST to "api.php?action=query&meta=tokens&type=csrf"
4. = POST to "api.php?action=edit&[…]"
I made a small code sample that you can find here .
With the 1st request I save the login-token and the cookie (from the
header). − This is working well.
Making the 2nd request I have to send "lgname", "lgpassword" and
"lgtoken" in the body and the cookie in the header. − But then I get the
"Fetching a token via action=login is deprecated. Use
The response includes the result ("NeedToken") and "token",
If I use the body-parameters as URL-parameters I get the API warning:
"The following parameters were found in the query string, but must be
in the POST body: lgpassword, lgtoken".
So I think I need to know:
Which steps/requests I have to do − with which: HTTP method, URL and
parameters, body data.
(Step 3 and 4 aren’t possible for me
Excuse me if that question(s) are more noobish …! − I read the
documentation and some mailinglist posts. But I couldn’t find any hint
of the ‚big picture‘ (of the process).
Thanks a lot (in advance for a solution) and best regards
looks like REL1_28 is broken. When you attempt to clone the extensions
directory, 2ColConflict is prompting for a password. (Ran into similar
issue in REL1_27 and it was because the extension was removed without the
proper backporting of removals)