Mediawiki-api August 2016

mediawiki-api@lists.wikimedia.org

7 participants
8 discussions

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] Deprecation of list=allusers 'recenteditcount' result property
by Brad Jorsch (Anomie) 16 Apr '19

16 Apr '19

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 _______________________________________________ Mediawiki-api-announce mailing list Mediawiki-api-announce(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce

1 1

[Mediawiki-api-announce] DEPRECATION: Passwords and other sensitive fields for authentication must be in the POST body
by Brad Jorsch (Anomie) 01 Nov '16

01 Nov '16

For improved safety, passwords and other sensitive fields for authentication should not be included in the request URI during a POST. Instead, they should be in the POST body where they are less likely to be included in log files. With the merge of Gerrit change 305545,[1] the API will now produce a warning if such fields are detected in the URI. This should be deployed to WMF wikis with 1.28.0-wmf.16, see https://www.mediawiki.org/wiki/MediaWiki_1.28/Roadmap for the schedule. This affects the following modules and fields: * action=login: 'lgpassword' * action=clientlogin, action=createaccount, action=linkaccount, and action=changeauthenticationdata: Any fields reported as "sensitive" by action=query&meta=authmanagerinfo or by UI or REDIRECT responses. Currently, this affects the 'password' and 'retype' fields. The 'lgtoken' field for action=login will now also issue a warning if placed in the request URI. The error code for other tokens being in the request URI has changed from 'mustposttoken' to 'mustpostparams'. To check if your client's user agent is detected making such submissions, you can also use ApiFeatureUsage[2] and look for '<action>-params-in-query-string' once 1.28.0-wmf.16 is rolled out to wikis your client is logging in to. It is planned that these warnings will be changed to errors during 1.29. Let's avoid having a repeat of T142155,[3] update your code ASAP instead of waiting until it breaks. Thanks. [1]: https://gerrit.wikimedia.org/r/#/c/305545/ [2]: https://meta.wikimedia.org/wiki/Special:ApiFeatureUsage [3]: https://phabricator.wikimedia.org/T142155 -- 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 1

Reg : Opensearch API Issue
by Rajesh S6 31 Aug '16

31 Aug '16

Dear Team, We are facing issue with opensearch if we are using name space either 0 or 6 individually it is working, if we use both name space using | this symbol we are not getting result. how to resolve this, for ex https://test.test.net/test/api.php?action=opensearch&format=json&formatvers… Thanks & Regards S. Rajesh =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

1 0

[Mediawiki-api-announce] New features: Alternative multi-value separator and Unicode normalization warnings
by Brad Jorsch (Anomie) 30 Aug '16

30 Aug '16

Both of these changes should be deployed to WMF wikis with 1.28.0-wmf.17, see https://www.mediawiki.org/wiki/MediaWiki_1.28/Roadmap for the schedule. == Alternative multi-value separator == With the merging of Gerrit change 305126,[1] if a value for a multi-valued parameter must contain pipe characters (U+007C, "|"), it will now be possible to use the Unit Separator character (U+001F) instead. As this character is not otherwise valid input for any strings in MediaWiki, its use here should not conflict with any valid input. To signal that you're using this feature, the whole multi-value parameter must also be prefixed with the Unit Separator character. For example, you can now use meta=allmessages to parse the "search-rewritten" message with the text "foo|bar" as $1 and "foo|baz" as $2: https://en.wikipedia.beta.wmflabs.org/w/api.php?action=query&meta=allmessag… <https://en.wikipedia.beta.wmflabs.org/w/api.php?action=query&meta=allmessag…> Client libraries should consider updating to use this feature when asked to send a multi-valued parameter with one or more values containing pipe characters. == Unicode normalization warnings == The API has always expected input as NFC-normalized Unicode represented as UTF-8. Non-NFC-normalized UTF-8 input would be silently normalized, and in the query string non-UTF-8 input would be interpreted as being in a fallback encoding (such as Windows-1252) and converted to Unicode. This sometimes led to subtle bugs when input was unexpectedly converted. With the merging of Gerrit change 306491,[2] the API will now issue a warning when input was subject to such conversion, which is hoped to make it more obvious to clients when their input was subject to conversion. When this happens in the 'titles' parameter for ApiPageSet-using modules, the response will also include the conversion of each title in the existing 'normalized' element. Since the API result cannot directly represent non-normalized data, these entries will have the 'from' element percent-encoded and a 'fromencoded' boolean will be included alongside to indicate this. This normalization step is separate from the existing Title normalization (uppercasing the first letter and replacing underscores with spaces), so two entries may be generated in the 'normalized' element. See https://en.wikipedia.beta.wmflabs.org/w/api.php?action=query&titles=a%CC%8A… for an example showing the new warning and normalization entries. [1]: https://gerrit.wikimedia.org/r/#/c/305126/ [2]: https://gerrit.wikimedia.org/r/#/c/306491/ -- 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] Section edit REST API end point to be replaced next week
by Gabriel Wicke 26 Aug '16

26 Aug '16

Hello, REST API users. We are planning to deploy a new REST API endpoint for section editing next week. This will replace the current /transform/sections/to/wikitext/ <https://en.wikipedia.org/api/rest_v1/#!/Transforms/post_transform_sections_…> end point, and will provide the same functionality in a more streamlined and extensible format. The existing end point is classified as unstable <https://www.mediawiki.org/wiki/API_versioning#Unstable>, which guarantees that we are making an effort to avoid breaking existing clients. According to our data, the end point is basically unused at present, which is why we are aiming at a fairly speedy deploy around Tuesday next week (Aug 30). If you are using this end point at present & have concerns about its removal, then let us know here. Best regards, the WMF Services Team <https://www.mediawiki.org/wiki/Wikimedia_Services>. -- Gabriel Wicke Principal 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

Finding out Wikidata item out of Wikipedia article via API
by Adrian Tineo 11 Aug '16

11 Aug '16

Hi all This is my first post in this list. I'm not clear if this is the best place for me to ask this question, so feel free to recommend some other contact point. Context: I am trying to find out via API what is the Wikidata item from a Wikipedia page. This is visible in the Tools side bar in the Wikipedia page but I can't figure out how to get this information from the API. Question: How can I get via API the Wikidata item matching a given Wikipedia article? Example: Say that the starting point is Albert Einstein's page in the English Wikipedia (https://en.wikipedia.org/wiki/Albert_Einstein). I can get the page content via API like so: https://en.wikipedia.org/w/api.php?action=query&format=json&titles=Albert Einstein&prop=revisions&rvprop=content I can get plenty of other info by using some other params to the query action. Some I have tried include: prop:extlinks, prop:info, meta:filerepoinfo, etc. None of these contain the Wikidata item matching the article though. I couldn't find out anything about it in the MediaWiki API help. As of now, the best I can do is: 1. Query Wikidata with the page title like so: https://www.wikidata.org/w/api.php?format=json&action=wbsearchentities&sear… Einstein&language=en 2. Browse through the output for the desired Albert Einstein entry among: * Q937, Albert Einstein, German-American physicist and founder of the theory of relativity * Q13426745, Albert Einstein, Studio album by Prodigy and The Alchemist * Q15990626, Albert Einstein, Wikimedia disambiguation page * 3 more entries This adds a complication, as I need the intelligence to tell which is the Wikidata item I was looking for, whereas in the Wikipedia page in the browser I can access the item (Q937) directly. Any help much appreciated. Regards, Adrian Tineo

2 2

API login
by John 08 Aug '16

08 Aug '16

Why in the hell has basic API logins stopped working? I now need to either set up an Oauth provider/client or use Special:Botpassword. Having a standard login option should be available, otherwise anyone who codes for using the API is going to get screwed. Apparently it will require setting up special permissions and login processes depending on what version of MW the wiki is using... Why cant we just keep a standard process and allow for more options?

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Mediawiki-api August 2016