Mediawiki-api

mediawiki-api@lists.wikimedia.org

1 participants
1265 discussions

Weird response from API when using generator
by Christoffer G. Thomsen 28 Jan '14

28 Jan '14

Hi I am trying to retrieve the categories of new pages via the API on the Danish Wikipedia using this API request: https://da.wikipedia.org/w/api.php?action=query&prop=categories&format=json… When I make that request, I get this response https://gist.github.com/cgtdk/e746b6042883b970c640 (a non-broken up version of the API request URL has been added to the gist as a comment). The interesting part is line 76 to 86. This is the response item for the page "VM i bandy 2015". It claims that this page only has one category, "Kategori:Fremtidige sportsbegivenheder", but it actually has had three categories ever since the first (and only, as of writing this) revision: Kategori:Fremtidige sportsbegivenheder, Kategori:VM i bandy, and Kategori:Sport i 2015. I have tried to do this several times (with minor modifications) both in the API Sandbox on dawiki and directly. When I query the page directly, like this: https://da.wikipedia.org/w/api.php?action=query&prop=categories&format=json… I get this response: https://gist.github.com/cgtdk/69e874cf7d3fae6ee506 which shows the correct category information for the page. What is going on? Am I doing something wrong or is there a bug? Thanks, Christoffer G. Thomsen (meta:User:Cgtdk)

2 2

[Mediawiki-api-announce] BREAKING CHANGE: Improved RevDel support
by Brad Jorsch (Anomie) 23 Jan '14

23 Jan '14

Gerrit change 107389[1] adds RevDel support to various API query modules, so for example a user with the 'deletedhistory' right will be able to retrieve the user and summary from prop=revisions. This will cause some changes: - list=deletedrevs, list=filearchive, list=recentchanges, and list=watchlist formerly would not return any information at all for entries where any field was revision-deleted. These entries will now be returned. "hidden" indicators will be provided as is done for modules such as prop=revisions. - prop=imageinfo, list=logevents, prop=revisions, and list=usercontribs will now return field values in addition to the "hidden" indicators, if the user has the necessary user rights. - When "hidden" indicators are returned, a new indicator "suppressed" may also be returned to indicate whether suppression was activated. - prop=imageinfo will now return info for revision-deleted files. - list=logevents, when searching by user or title, will no longer skip revisions where the user or title was revision-deleted if the requesting user has the deletedhistory right. - list=usercontributions will now look at the correct user rights (deletedhistory and suppressrevision, not hideuser) to determine whether to hide revision-deleted contributions. All clients should be updated to expect rows with hidden fields for deletedrevs, filearchive, recentchanges, and watchlist, and clients with advanced permissions should be updated to properly handle (and to not publicly reveal) the data for revision-deleted fields from these modules as well as imageinfo, logevents, revisions, and usercontribs. These changes will be deployed to WMF wikis with 1.23wmf11, see https://www.mediawiki.org/wiki/MediaWiki_1.23/Roadmap for the schedule. [1]: https://gerrit.wikimedia.org/r/#/c/107389/ -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation _______________________________________________ Mediawiki-api-announce mailing list Mediawiki-api-announce(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce

2 2

Random Article
by Max Ilnitskiy 23 Jan '14

23 Jan '14

Hi guys. My name is Max, and i'm iOS developer. I want make "random article" button for iOS. But i don't understand, how does wikipedia random article works. How can i made it? And how can i made random, only in one category? Has article id data about category, or this data are contained in individual properties? Thanks Max Ilnitskiy

2 3

Guidance Needed!!! To call the API from Codecademy to edit wiki pages
by Diwanshi Pandey 21 Jan '14

21 Jan '14

Hello All, I am Diwanshi Pandey, an OPW intern working on the project "Completing mediawiki API development course on Codecademy" . I have completed Parsing and Querying aspects of API but stuck with Modifications as i don't have required permissions. The link to the course: http://www.codecademy.com/courses/web-intermediate-en-BLea4/4/1 I was trying to get an edit token but there was a warning saying: "Unrecognized value for parameter 'intoken': edit" The reason of this issue is certainly because of "callback" parameter. I have also filed a bug as the above warning is unclear. In my course, I want to cover getting a token , editing a page , add a page to watchlist , etc but not deleting a page. I am blocked by this isuue. Does anybody know some other way to code it? or Can someone guide me through some other process? Thanks -- *Regards,* *Diwanshi Pandey*

2 3

Re: [Mediawiki-api] How to know the API changes
by Brad Jorsch (Anomie) 15 Jan '14

15 Jan '14

On Tue, Jan 14, 2014 at 5:47 AM, Xia Zhang <xiazhang(a)google.com> wrote: > > From you previous email. You have a QA instance > https://deployment.wikimedia.beta.wmflabs.org/wiki/Main_Page. > I have another question: How frequent you update the QA instance? Is it a > reliable/final QA instance before pushing it to production instance? Or > still involves in some bug-fix-cycle to the QA? > beta.wmflabs.org is updated continuously as changes are merged into the git repository. -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation

3 3

[Mediawiki-api-announce] Changes to 'assert' handling on WMF wikis
by Brad Jorsch (Anomie) 06 Jan '14

06 Jan '14

The AssertEdit extension has long been installed on WMF wikis, allowing bots to include "&assert=user" or "&assert=bot" in their action=edit requests to prevent accidentally editing while logged out. With Gerrit change 90263,[1] the functionality will be included in MediaWiki core. At the same time, the following changes will be made to the functioning of this feature: * Assertion will be available on all API actions, not just edit. * Assertion failure will now be indicated by an API error, code 'assertbotfailed' or 'assertuserfailed'. * The 'nassert' parameter will be ignored, and using it will give an unrecognized parameter warning. * Other assertions, such as 'true', 'false', and 'exists', will no longer function and attempting to use them will result in an 'unknown_assert' error. Most clients should notice little change from this transition besides the fact of receiving an error rather than a failure status from action=edit. This change will be rolled out with 1.23wmf10, see https://www.mediawiki.org/wiki/MediaWiki_1.23/Roadmap for the schedule. [1]: https://gerrit.wikimedia.org/r/#/c/90263/ -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation _______________________________________________ Mediawiki-api-announce mailing list Mediawiki-api-announce(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce

1 0

How to know the API changes
by Liu Chenheng 06 Jan '14

06 Jan '14

Hi, All, I'd like to be notified as soon as the API changes. A simple way is to monitor the page http://en.wikipedia.org/w/api.php Here is my problem: Will the page http://en.wikipedia.org/w/api.php be always updated when the API changes (i.e. add/remove some new params) or the format of the response changes. If not, are there any ways to monitor that? Thanks.

2 3

[Mediawiki-api-announce] Change to action=upload warnings
by Brad Jorsch (Anomie) 04 Jan '14

04 Jan '14

When uploading files via the API, various warnings may be returned. One of these warnings is "deleted-archive", with a value indicating the title under which the file was previously uploaded and deleted. With the merge of Gerrit change 105215,[1] which fixes bug 59167,[2] this "deleted-archive" warning may have an empty value when the file content has been suppressed. Clients should be adjusted to account for this possibility. [1]: https://gerrit.wikimedia.org/r/#/c/105215/ [2]: https://bugzilla.wikimedia.org/show_bug.cgi?id=59167 -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation _______________________________________________ Mediawiki-api-announce mailing list Mediawiki-api-announce(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce

1 0

Dealing with captchas as part of a "createaccount" API request
by Jeff Hall 04 Jan '14

04 Jan '14

I couldn't find any relevant documentation for this particular case, so I'm hoping someone on the list might be able to point me in the right direction... If I want to l create a new user account via the Mediawiki API, I might issue an initial request for a token like this: curl -c cookies.txt -X POST 'http://en.wikipedia.beta.wmflabs.org/w/api.php?action=login&format=json&lgn…' ...and then submit the actual request to create the account with the valid token obtained in the previous step: curl -b cookies.txt -X POST 'http://en.wikipedia.beta.wmflabs.org/w/api.php?action=login&format=json&lgn…<token_goes_here>' My problem is that some wikis require a captcha for account creation, so that second request gets a response like this: {"servedby"=>"deployment-apache33", "error"=>{"code"=>"Incorrect or missing CAPTCHA.", "info"=>"<Incorrect or missing CAPTCHA.>"}} I'm don't know how to deal with the captcha requirement via my API calls. Does anyone know if that is possible with a "createaccount" request, and if so, how does that work? Thanks, Jeff

2 1

About the recent change list
by Liu Chenheng 02 Jan '14

02 Jan '14

Hi, All, We can only get the recent changes from API. But I found we only could get the recent changes which happened during the last 30 days. How can I get the recent changes earlier than 30 days? Or are there any pages or statements about this? Thanks. Ethan Liu

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Mediawiki-api