Mediawiki-api September 2019

mediawiki-api@lists.wikimedia.org

2 participants
5 discussions

How to expand templates, but leave comments
by Kevin Dunn 20 Jan '26

20 Jan '26

Hi there, I'm using the API to extract the raw wiki text from my pages, using the "?action=query&titles=Main_Page&export&exportnowrap" syntax. That works perfectly. Now I would like to get the templates expanded out in the result, so I use: "?action=query&titles=Main_Page&prop=revisions&rvlimit=1&rvprop=content&rvexpandtemplates", which does the job, as expected, but it also strips out the comments. My problem is that the comments are meaningful to me (I use them to help process the wiki text in subsequent steps). Is there a way to expand templates with the API, but leave the comments intact? Thanks, Kevin

4 5

Need to extract abstract of a wikipedia page
by aditya srinivas 23 Nov '23

23 Nov '23

Hello, I am writing a Java program to extract the abstract of the wikipedia page given the title of the wikipedia page. I have done some research and found out that the abstract with be in rvsection=0 So for example if I want the abstract of 'Eiffel Tower" wiki page then I am querying using the api in the following way. http://en.wikipedia.org/w/api.php?action=query&prop=revisions&titles=Eiffel… and parse the XML data which we get and take the wikitext in the tag <rev xml:space="preserve"> which represents the abstract of the wikipedia page. But this wiki text also contains the infobox data which I do not need. I would like to know if there is anyway in which I can remove the infobox data and get only the wikitext related to the page's abstract Or if there is any alternative method by which I can get the abstract of the page directly. Looking forward to your help. Thanks in Advance Aditya Uppu

4 3

[Mediawiki-api-announce] BREAKING CHANGE: Format of blockexpiry timestamps from list=users and list=allusers
by Brad Jorsch (Anomie) 19 Sep '19

19 Sep '19

The format of block expiry timestamps returned from list=users and list=allusers has long been inconsistent. It was being returned in an internal format (e.g. "20190918201053"), rather than the ISO 8601 format used by the rest of the API (e.g. "2019-09-18T20:10:53Z"). The 'blockexpiry' property from these two modules will be changing to the standard ISO 8601 format with 1.34.0-wmf.24. See https://www.mediawiki.org/wiki/MediaWiki_1.34/Roadmap for a schedule of deployment to Wikimedia wikis. This change also brings the block information returned by list=users and list=allusers fully in line with that already used for meta=userinfo and 'blocked' errors from various actions. -- Brad Jorsch (Anomie) Senior 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

[Mediawiki-api-announce] BREAKING CHANGE: Reporting of edit failures due to AbuseFilter and SpamBlacklist
by Brad Jorsch (Anomie) 11 Sep '19

11 Sep '19

When saving an edit is prevented by the AbuseFilter or SpamBlacklist extensions, the error is currently reported as a successful API response with a 'failure' code in the body.[1][2] In the future, these will be reported as standard API errors.[3][4] This change should be deployed to Wikimedia wikis with 1.34.0-wmf.23. See https://www.mediawiki.org/wiki/MediaWiki_1.34/Roadmap for a schedule. Clients that do not need to specially handle failures due to AbuseFilter or SpamBlacklist will likely need no changes, as they probably already include code to generically handle API error responses. Clients that do handle AbuseFilter or SpamBlacklist failures specially will need to be updated to check for error codes 'abusefilter-warning', 'abusefilter-disallowed', and/or 'spamblacklist' and handle them as they do the current AbuseFilter and SpamBlacklist failures, if they want to preserve their current special handling. Note that edit failures due to CAPTCHAs from ConfirmEdit are not being changed at this time. They will continue to be reported as before.[5] [1]: AbuseFilter: https://phabricator.wikimedia.org/P8988 [2]: SpamBlacklist: https://phabricator.wikimedia.org/P8990 [3]: AbuseFilter: https://phabricator.wikimedia.org/P8989 [4]: SpamBlacklist: https://phabricator.wikimedia.org/P8991 [5]: ConfirmEdit: https://phabricator.wikimedia.org/P9076 -- Brad Jorsch (Anomie) Senior 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

empty extract field with exintro=True
by Bertel Teilfeldt Hansen 10 Sep '19

10 Sep '19

Hi Mediawiki-api mailing listers! I'm trying to get the intro to a list of Wikipedia pages using the "extracts" property with "exintro=True". This works fine for most sites, but for a few of them the API returns an empty extract field. See for example: https://en.wikipedia.org/w/api.php?action=query&prop=extracts&titles=Anthem… When looking at the page "https://en.wikipedia.org/wiki/Anthem" there definitely seems to be text before the first section, so I think I should be getting something. Indeed without the "exintro" parameter, I get the expected return. Any idea why this occurs? Best, Bertel

2 2

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Mediawiki-api September 2019