Mediawiki-api

mediawiki-api@lists.wikimedia.org

1264 discussions

Proposal to deprecate parsing and diffs in the action API action=query&prop=revisions
by Brad Jorsch (Anomie) 29 Apr '17

29 Apr '17

TL;DR: I'm proposing deprecating a bunch of parameters. See https://phabricator.wikimedia.org/T164106. 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 situation. 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 development. 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 Wikimedia Foundation

1 0

Action=clientLogin issue
by Mujtaba Rafiq 23 Apr '17

23 Apr '17

Hello everyone, I am trying to login using action=clientlogin via javascript Ajax call and backend as well but for some reason I am always getting same error { "code": "badtoken", "info": "Invalid CSRF token.",....} If I use same parameters and call from POSTman it works and I get logged in. What could be wrong? Am I missing something thats not required by call from POSTman. I also posted the same question on API talk <https://www.mediawiki.org/wiki/API_talk:Login#action.3Dclientlogin> This is the link to the code for reference Link to github java code <https://github.com/Institute-Web-Science-and-Technologies/okb-toollabs/blob…> Thank you, Mujtaba Rafiq

1 0

Get all users per API
by Dennis Roczek 21 Apr '17

21 Apr '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, 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? Regards, Dennis Roczek -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJY+euWAAoJEM4+Qf3OKrbZFo8QAMp9gw53RBPodG1VPZCCfnjf L6IJnPEuSH1aVPiaPBMoQnEdhN6Eh7TDIpNDxu9AUPv3+ExLCIztqfh9ZhpTxBJ/ DjaLJsLOxYoR4kutXv55shKowuZK2l1zti+4KtwtVknHiT60Mf6pQWti86fwg+eJ S2OmVuzWZK39zFHTeuXePkWEb80JOO7DNZokvzRjHXYGPvzVymb596ZZB76h4cM9 ah+hdLRAkJOM3iwzl/Av3pj5ECrfbq1hBCDQGuPp2xMWSQkb5tR2NVBbYnf2TCuE HwR7DqcVxskEgWU1IEVVq3oKIZIqrLAZg9vIJG3/tV3RekSYDDPSdH4P2b4yuC6S 4Qg2MQnnr8Q2TDDhTc8c3q9qRa20FOKQ7IZhi7E6O6oVY64JiAxT+f9MeFQYMAgO DEsirpxxOr+sXZYp5pBBfQbjdYIKx1Ety/+ab4uXOZVrleNr0U+tcGd3U42GL9DE 1oIaJTT9iGkh483hF8ttPNt+9KwCCOqzWRgYghkD0BftjepOjTlyjYS3RSd0RsEj QFCegZqKDkTHA2N75IT5GT9pLW5HHgjPUS1XKRdyB4bjVl8Uxb0eR9XDLWOCuXPa rIkoox8hcYlsMSLjwfW+SZUaPBmQ27dJYtRpTx3RH07acy1jVuuYNgbtaVr9xV4L IGl4kWjB1ezsiqWqoHcM =EkcI -----END PGP SIGNATURE-----

2 1

How does yourdictionary obtains structured information from Wiktionary?
by Furkan Gözükara 17 Apr '17

17 Apr '17

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? For example page : https://en.wiktionary.org/wiki/game some structured information from yourdictionary . com http://imgur.com/a/FZHGW 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?

2 2

Re: [Mediawiki-api] How does yourdictionary obtains structured information from Wiktionary?
by Martin Domdey 17 Apr '17

17 Apr '17

1 0

API login (and edit) with BotPassword not possible
by Kai Sommer 13 Apr '17

13 Apr '17

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 [0]. My goal is to edit and create pages with my bot. [0] <https://github.com/nategood/httpful/> 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 [1]. [1] <https://pastebin.com/AX9fuxRX> 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 API warning: "Fetching a token via action=login is deprecated. Use action=query&meta=tokens&type=login instead." The response includes the result ("NeedToken") and "token", "cookieprefix", "sessionid". 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 Kai

2 1

REL1_28 issue
by John 12 Apr '17

12 Apr '17

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)

3 5

How can i learn which pages redirects to a certain page
by Furkan Gözükara 09 Apr '17

09 Apr '17

Hello. For example i would like to learn which pages redirects to this particular page The page is : https://tr.wikipedia.org/wiki/T%C3%BCrkiye_B%C3%BCy%C3%BCk_Millet_Meclisi The pages redirect that page for example : https://tr.wikipedia.org/wiki/TBMM So i want to lern via API that TBMM redirects to actually Türkiye Büyük Millet Meclisi Which means TBMM is abbreviation of Türkiye Büyük Millet Meclisi Also can i learn it is abbreviation or not by api?

2 2

Re: [Mediawiki-api] Wikipedia most viewed pages data
by Michael Holloway 07 Apr '17

07 Apr '17

Whoops! Meant to reply to list. On Fri, Apr 7, 2017 at 10:20 AM, Michael Holloway <mholloway(a)wikimedia.org> wrote: > Hi Anand, > > It looks like the results from those two queries are from different days. > The first set is from April 5 and the second is from April 6. For the > results from April 5 in the REST API, you'll want > https://en.wikipedia.org/api/rest_v1/feed/featured/2017/04/06. > > Also please note that the results from the Action API (api.php) aren't > sorted in decreasing pageview order as the REST API's are. You'll need to > sort them yourself. (Depending on the number of results you need, you > should also familiarize yourself with query continuation > <https://www.mediawiki.org/wiki/API:Query#Continuing_queries> as well as > the result limits per request on the various modules you're using (for > instance, 20 for TextExtracts and 50 for PageImages as indicated at the > bottom of the results of your query)). > > After ensuring you have the same date and sorting the Action API results, > you should have the same or very similar results. For instance, looking at > the results from April 5, it looks like "Lake Nyos Disaster" is on top > with 497638 pageviews in both sets. You still might see slight > discrepancies between the two sources due to implementation details, > however; for instance, in the REST API endpoint we use a heuristic to > attempt to filter out pages with pageview counts likely inflated by bot > traffic, and so a few pages here and there that appear in the Action API > results wouldn't appear in the REST API list. > > Best, > Michael > > On Fri, Apr 7, 2017 at 6:02 AM, Anandroid Inc <anandrdinc(a)gmail.com> > wrote: > >> Hi Team, >> >> Thanks a lot for your support and quick responses. >> As per all the suggestions you gave for my query, I found below two apis >> which solves my purpose, >> But I see both queries ask for todays most viewed pages on wikipedia but >> they are returning different results. >> Request you to please help me on this. >> >> 1) >> https://en.wikipedia.org/w/api.php?action=query&format=json& >> prop=extracts%7Cinfo%7Cpageimages%7Cpageviews%7Cpageterms% >> 7Cpageprops%7Crevisions&generator=mostviewed&exchars= >> 512&exlimit=max&exintro=1&explaintext=1&exsectionformat=plai >> n&inprop=url&pithumbsize=640&pilimit=max&wbptterms=descript >> ion%7Calias%7Clabel&gpvimlimit=50&pvipdays=1 >> <https://en.wikipedia.org/w/api.php?action=query&format=json&prop=extracts%7…> >> >> 2) https://en.wikipedia.org/api/rest_v1/feed/featured/2017/04/07 >> >> >> >> On 07-Apr-2017, at 3:43 AM, Adam Baso <abaso(a)wikimedia.org> wrote: >> >> For the action API I think you're looking for an extra property, >> *pageviews*. Maybe something like this: >> >> https://en.wikipedia.org/wiki/Special:ApiSandbox#action=quer >> y&format=json&prop=extracts%7Cinfo%7Cpageimages%7Cpageview >> s%7Cpageterms%7Cpageprops%7Crevisions&generator=mostviewed&exchars=512& >> exlimit=max&exintro=1&explaintext=1&exsectionformat=plain& >> inprop=url&pithumbsize=640&pilimit=max&pvipdays=8&wbptter >> ms=description%7Calias%7Clabel&gpvimlimit=20 >> >> On Thu, Apr 6, 2017 at 4:44 PM, Anandroid Inc <anandrdinc(a)gmail.com> >> wrote: >> >>> ++Michael >>> >>> On 07-Apr-2017, at 3:09 AM, Anandroid Inc <anandrdinc(a)gmail.com> wrote: >>> >>> Hi Michael, >>> >>> Thanks for your quick response. >>> This is very helpful, exactly what I was looking for. >>> >>> Thanks, >>> Anand >>> >>> On 07-Apr-2017, at 12:08 AM, Michael Holloway <mholloway(a)wikimedia.org> >>> wrote: >>> >>> Hi Anand, >>> >>> It sounds like the REST API's featured feed endpoint >>> <https://en.wikipedia.org/api/rest_v1/#!/Feed/aggregatedFeed> provides >>> what you're looking for. >>> >>> For example: https://en.wikipedia.org/api/r >>> est_v1/feed/featured/2017/04/06 (see the content under the "mostread" >>> key). >>> >>> Under the hood, titles are obtained from the Pageview API >>> <https://wikitech.wikimedia.org/wiki/Analytics/PageviewAPI> and then >>> supplementary information for our desired titles is obtained from the REST >>> API's page summary endpoint >>> <https://en.wikipedia.org/api/rest_v1/#!/Page_content/get_page_summary_title>. >>> That would be the easiest way to go if you'd like to go in a slightly >>> different direction from what's provided in our featured feed endpoint. >>> >>> If you'd like, you can view the implementation for the "mostread" >>> section of our aggregated feed endpoint here: >>> >>> https://phabricator.wikimedia.org/diffusion/GMOA/browse/mast >>> er/lib/feed/most-read.js >>> >>> Please note that as of now the REST API endpoints are officially >>> designated as unstable. >>> >>> Best, >>> Michael >>> >>> >>> >>> On Thu, Apr 6, 2017 at 2:19 PM, Anandroid Inc <anandrdinc(a)gmail.com> >>> wrote: >>> >>>> Hi Team, >>>> >>>> Thanks for the great api provided for all the wiki info. >>>> I am looking for a combination of right parameters which will return me >>>> most viewed pages with the page url, article snippet, thumbnail image url. >>>> Hope you can help with this. >>>> >>>> Thanks, >>>> Anand >>>> _______________________________________________ >>>> Mediawiki-api mailing list >>>> Mediawiki-api(a)lists.wikimedia.org >>>> https://lists.wikimedia.org/mailman/listinfo/mediawiki-api >>>> >>> >>> _______________________________________________ >>> Mediawiki-api mailing list >>> Mediawiki-api(a)lists.wikimedia.org >>> https://lists.wikimedia.org/mailman/listinfo/mediawiki-api >>> >>> >>> >>> >>> _______________________________________________ >>> Mediawiki-api mailing list >>> Mediawiki-api(a)lists.wikimedia.org >>> https://lists.wikimedia.org/mailman/listinfo/mediawiki-api >>> >>> >> _______________________________________________ >> Mediawiki-api mailing list >> Mediawiki-api(a)lists.wikimedia.org >> https://lists.wikimedia.org/mailman/listinfo/mediawiki-api >> >> >> >

2 2

Wikipedia most viewed pages data
by Anandroid Inc 07 Apr '17

07 Apr '17

Hi Team, Thanks for the great api provided for all the wiki info. I am looking for a combination of right parameters which will return me most viewed pages with the page url, article snippet, thumbnail image url. Hope you can help with this. Thanks, Anand

4 8

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Mediawiki-api