October 2008 - Mediawiki-api - lists.wikimedia.org

API to access viewcount?
by Jim Tittsler 30 Apr '09

30 Apr '09

How can I access the 'viewcount' property of a page?

4 6

API Implementation - Critique
by Mark Henderson 20 Feb '09

20 Feb '09

I need some help - I've implemented the API using CodeIgniter for a clients site and everything works on the site except for the wiki pages, which are sluggish. Here is my controller which lists the function calls being made and in what order: http://pastebin.com/m4021c1a7 And here is my model where the actual API calls are made: http://pastebin.com/dd7c504c The api.php file exists on the same server that is making the calls, so it should be instant but the pages are so very slow, and only in the instance of using the MW API. Any help or insight anybody could give would be MUCH appreciated. - Mark

4 7

List of all authors via API
by Johannes Beigel 01 Nov '08

01 Nov '08

We're heavily using the MediaWiki API in our opensource project mwlib (http://code.pediapress.com/ ), so first of all: Thanks to you all for implementing this functionality to MediaWiki! Maybe you're following the discussion initiated by Erik Möller on Foundation-l about appropriate attribution. As there is yet a consesus to be found, we plan to include all authors (minus minor edits, minus bots) after each article in documents (PDFs, ODFs) rendered from article collections. Currently we're using an API query with prop=revisions, requesting rvprop=user|ids|flags. Afterwards we're filtering out minor edits, anonymous/IP edits and bot edits (via regular expression on username and comment) and combine edits by the same author. To retrieve the data for all revisions for heavily edited articles (e.g. [[en:Physics]]), this requires lots of API requests with rvlimit=500. Is there a way (or a plan to implement one) to retrieve the list of unique contributors for a given article (from a given revision down to the first one)? Ideally this would accept parameters for the mentioned filtering. I guess inside of MediaWiki code this can be handled very efficiently (using appropriate database queries) and would eliminate the need to transfer lots of redundant data over the socket. -- Johannes Beigel

5 7

Amazon File Repo
by Daniel Friesen 31 Oct '08

31 Oct '08

Before I decide to work on it sometime in the future, anyone else interested in creating a LocalFileRepo for Amazon's API? Unless someone corrects me, the best method of dealing with Amazon S3 for storing images would be to make use of S3's API, rather than mounting buckets onto the filesystem. The former should be more reliable (^_^ trying to use a mountpoint will probably drive someone up the wall like NFS does for brion), and also using the API should be more reliable for handling multiple buckets, since as I recall the Amazon docs say that buckets can only hold up to 5Gb each. Though considering the large things to deal with for multiple buckets, and the fact that the best methods will probably also have some url redirect handling as well to keep the standard urls, it might be best as an extension rather than put into core. -- ~Daniel Friesen (Dantman, Nadir-Seen-Fire) ~Profile/Portfolio: http://nadir-seen-fire.com -The Nadir-Point Group (http://nadir-point.com) --It's Wiki-Tools subgroup (http://wiki-tools.com) --The ElectronicMe project (http://electronic-me.org) -Wikia ACG on Wikia.com (http://wikia.com/wiki/Wikia_ACG) --Animepedia (http://anime.wikia.com) --Narutopedia (http://naruto.wikia.com)

1 0

Getting strange characters at action_parse
by Rainer Terhart 29 Oct '08

29 Oct '08

Hello, i don not know, if i am right here, but i got a strange parse-response from wikiparser today. Maybe one can have a look on it. (i am from germany and i used wikis api.php for parsing the entry("Baum"); here is the request i used: http://de.wikipedia.org/w/api.php?action=parse&prop=text&format=xml&page=ba… this should be the last parsed text: "" actually, api.php adds more text at the end of the response. <a href="/w/index.php?title=Af:Boom&....................class="new" title="Zh-yue:樹 (Seite nicht vorhanden)">zh-yue:樹</a> In the browser, this is shown as very strange HTML-Text. Did i made something wrong? This only happens at the page=Baum Greetings Raenaet _______________________________________________________________________ Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 30 Tage kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=022220

4 4

using a newer version of API with older Mediawiki install?
by . . 28 Oct '08

28 Oct '08

Hi all, I haven't found an answer to this elsewhere, so I'm posing the question here. Is it possible to use a newer version of the mediawiki api (perhaps by copying api.php from a newer version) with an older MW installation? I am on MW 1.12 and would like to use the edit feature introduced in MW 1.13, but without the effort of upgrading our entire wiki. Is this possible? Thanks for your help. Matthew

3 3

[Mediawiki-api-announce] BREAKING CHANGE: Providing prop=revisions&rvprop=content with too many titles or revisions causes warning instead of error
by Roan Kattouw 24 Oct '08

24 Oct '08

As of r42471 [1], prop=revisions&rvprop=content will no longer throw an error when too many titles or revisions are specified, but will throw a warning and ignore the superfluous titles/revisions. The warning message is identical to the one issued when too many values are specified for the titles or revids parameter. This change was made to fix bug 16074 [2], which occurred when a generator with gXXlimit=max (or any sufficiently high limit, really) was used to feed prop=revisions&rvprop=content, which would then throw an error because it was fed too many titles or revisions. However, the generator is not aware that prop=revisions threw away most of its results, and will set a query-continue as if this didn't happen. If this query-continue value is used by the client, a (potentially large) number of results will be skipped. When continuing such a request (i.e. one with a generator feeding prop=revisions&rvprop=content with a high or maximum limit), you have to set gXXlimit to a sufficiently low value first, so prop=revisions doesn't receive too many results and doesn't throw stuff away. The right number can be found in the text of the warning message, which is always something like "Too many values supplied for parameter 'titles': the limit is 50" (note that both 'titles' and the number 50 may vary). Finally, it should be noted that this behavior can only occur with prop=revisions&rvprop=content and only when a generator is used to feed it. All other modules and all uses of prop=revisions not involving both rvprop=content and a generator are not affected. Roan Kattouw (Catrope) [1] http://www.mediawiki.org/wiki/Special:Code/MediaWiki/42471 [2] https://bugzilla.wikimedia.org/show_bug.cgi?id=16074 _______________________________________________ Mediawiki-api-announce mailing list Mediawiki-api-announce(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce

1 0

editing and timestamp confusion
by Jools Smyth 24 Oct '08

24 Oct '08

I am slightly confused over the editing of a page and avoiding a conflict using the api. The documentation says "To edit a page, an edit token is required. This token is the same for all pages, but changes at every login. If you want to protect against edit conflicts (which is wise), you also need to get the timestamp of the last revision. You can obtain these as follows:" And I had implemented this literally, so that on submitted the edit, I first get the timestamp of the very last revision and then submit my changes. But I assume I really need to Get page contents and store the timestamp - make some changes to the page. when I edit pass my timestamp back to the API. Is this correct? If so, maybe the documentation would be better to say "you also need the timestamp of the revision your edits are based on" ? Best Regards Jools

7 14

Accessing Template Fields
by Brendan Crosser-McGay 17 Oct '08

17 Oct '08

I looked through the API docs I found online, and I didn't see any straightforward way to access template fields on a page through any obvious means. As an example, I want to access a page, pull in values from a number of different pre-defined wiki-page-template fields. Is there any way to do this, or am I stuck doing regex on a big blob of text? Thanks, Brendan

3 3

How can i use longitude and latitude get the nearby articles from wiki
by Lv Jiajun 16 Oct '08

16 Oct '08

hi all, How can i use longitude and latitude get the nearby articles from wiki ? -- Kind Regards, Neil Skype: anim510 Twitter: anim510 Email: lvjiajun(a)nibirutech.com Email: anim510(a)163.com

2 1

Get a list of all pages containing a given template
by Ian Pye 16 Oct '08

16 Oct '08

Hi, Is it possible to generate a list which contains all the pages which use a given template? Thanks, Ian

2 1

Snippets when searching
by Manuel Fernandez Sanchez de la Blanca 14 Oct '08

14 Oct '08

Hi, all. Is there some way of retrieving a snippet/summary of documents when performing a search? Let me explain better. For example, when using *api.php?action=query&list=search&srwhat=text&srsearch=cvs&format=xml ,*the result is *<api> <query> <search> </search> </query> </api>* And I would like to get something as: *<api> <query> <search> ...bla bla cvs bla bla instalar ... cvs bla bla... ...blabla bla lista tareas bla bla... </search> </query> </api>* Is it possible? Thank you. -- Manuel Fernández Sánchez de la Blanca

3 3

MW API set cookies when using internal calls
by Dian 13 Oct '08

13 Oct '08

Hi all, I am trying to create a new layer for the MW API which allows access over SOAP. I plan to support some often used functions like: *login / logout *create / delete a page *read / update a page *move a page For each function I create a query and execute it using the created ApiMain object. When requesting an action the user should send the cookies (and the different tokens). In order to execute the action with proper user credentials set, I need to set the right cookies. Which is the best way to set the cookies in the wiki when communicating directly over ApiMain? Any suggestions appreciated! Best regards, Dian

3 4

Re: [Mediawiki-api] GPL/ Linking application against REST API requires to open the source
by Volz Raphael 09 Oct '08

09 Oct '08

Platonides, Ran, Roan, thanks for your feedback. We have built our own client code, communicate via sockets, and live on a completely different server in Java, so I assume that I can safely use the API. Thanks again for your insight. Raphael

1 0

GPL/ Linking application against REST API requires to open the source
by Volz Raphael 08 Oct '08

08 Oct '08

Hi - I am a bit unsure about whether it is OK to have an external application calling the MediaWiki API and being able to maintain that this application is proprietary. Does usage of the API trigger the virality of GPL ? We can work around by talking directly to MySQL instead, but using the REST API would be much more elegant and change resistant. Thanks for your insights. Thanks Raphael

4 3

Making API work on a local Wikipedia installation?
by Johann Petrak 08 Oct '08

08 Oct '08

I have installed MediaWiki 1.11.0 locally and loaded the english Wikipedia data into the local MySQL tables. The standard procedure for creating a local Wikipedia copy only creates the page, revision, and text tables. I have also installed the Cite, ExtensionFunctions, and ParserFunctions extensions. When I browse to localhost/wiki/api.php I get the help page for the api, but all requests I try return empty results (not an error). Which additional tables or extensions do I need to get this to work locally? Cheers, Johann

3 3

Re: [Mediawiki-api] Problem with action=edit
by Marcus Ramsden 06 Oct '08

06 Oct '08

It should work from version 1.13. Ensure that in your LocalSettings.php you have $wgEnableAPI and $wgEnableWriteAPI both set to true. Marcus From: mediawiki-api-bounces(a)lists.wikimedia.org [mailto:mediawiki-api-bounces@lists.wikimedia.org] On Behalf Of javi bueno Sent: 06 October 2008 14:15 To: mediawiki-api(a)lists.wikimedia.org Subject: [Mediawiki-api] Problem with action=edit Hi! I want to use the edit action of the api and I have a problem with it. I can't find what version of mediawiki I have to use due to I cannot see this feature in the api description. I have downloaded several versions of the mediawiki (1.13, 1.14alpha ...) and when I use ( action=edit ) an error like the following one is shown on the screen : <?xml version="1.0" encoding="utf-8"?> <api> <error code="unknown_action" info="Unrecognized value for parameter 'action': edit"> ... Anyone knows what version I have to download ? Thanks. _____ ¡Trónchate de risa con los mejores capítulos de South Park en MSN Vídeo! <http://video.msn.com/?mkt=es-es&vid=42a9e969-45ad-4c31-bff9-57629e71fac8&pl aylist=videoByUuids:uuids:e1daa69b-331b-4e99-8325-c936aaee9f97%2Cad4cb47a-90 a8-4b2c-88da-116d2059f4a2%2Cddaade1e-82b2-4914-8277-35e45198f5c6%2C42860247- e337-4384-94d8-fa444cb4aea7&from=hotmail&tab=s1207179071824>

3 2

Problem with action=edit
by javi bueno 06 Oct '08

06 Oct '08

Hi! I want to use the edit action of the api and I have a problem with it. I can't find what version of mediawiki I have to use due to I cannot see this feature in the api description. I have downloaded several versions of the mediawiki (1.13, 1.14alpha ...) and when I use ( action=edit ) an error like the following one is shown on the screen : <?xml version="1.0" encoding="utf-8"?><api> <error code="unknown_action" info="Unrecognized value for parameter 'action': edit"> ... Anyone knows what version I have to download ? Thanks. _________________________________________________________________ ¡Entra en el Club oficial de Messenger y te enterarás de todas las novedades! http://www.vivelive.com/ilovemessenger

1 0

[Mediawiki-api-announce] BREAKING CHANGE: action=protect to allow multiple expiries; output format, error messages changed
by Roan Kattouw 04 Oct '08

04 Oct '08

As of r41652 [1], action=protect allows the user to specify different expiry timestamps for different protections, something the UI has supported for a while. To support this, the expiry parameter has changed to accept multiple values, and even duplicate values. The first expiry timestamp will apply to the first protection, the second to the second, etc. The number of values in the expiry parameter must be equal to the number of values in the protections parameter, or an error will occur (for details on the new error message, see [2]). To preserve backwards compatibility, setting a single value in the expiry parameter is always allowed: in that case, all specified protections will have the same expiry timestamp. Example requests: api.php?action=protect&token=123ABC&title=Foo&protections=edit=sysop|move=sysop&expiry=infinite Will add the protections edit=sysop and move=sysop, both of which will never expire api.php?action=protect&token=123ABC&title=Foo&protections=edit=autoconfirmed|move=sysop&expiry=20081104000000|infinite Will add the protections edit=autoconfirmed and move=sysop; the first will expire on November 4, 2008, the second will never expire api.php?action=protect&token=123ABC&title=Foo&protections=edit=autoconfirmed|move=sysop|read=user&expiry=20081104000000|infinite Will cause an error, because 2 expiries were given for 3 protections api.php?action=protect&token=123ABC&title=Foo&protections=edit=autoconfirmed|move=sysop&expiry=20081104000000|infinite|infinite Will cause an error, because 3 expiries were given for 2 protections The output format has also been changed, so multiple expiry times can be listed. Old format: <protect title="Foo" reason="" expiry="infinite"> <protections edit="sysop" move="sysop" /> </protect> New format: <protect title="Foo" reason=""> <protections> <protection edit="sysop" expiry="infinite" /> <protection move="sysop" expiry="infinite" /> </protections> </protect> Additionally, the invalidexpiry and pastexpiry error messages have been changed to mention the expiry timestamp they're referring to. In the new messages, EXPIRY is replaced by the faulty expiry timestamp. Old messages: * code: invalidexpiry ** info: Invalid expiry time * code: pastexpiry ** info: Expiry time is in the past New messages: * code: invalidexpiry ** info: Invalid expiry time ``EXPIRY'' * code: pastexpiry ** info: Expiry time ``EXPIRY'' is in the past For the newly added error message toofewexpiries or more information about action=protect, see the documentation at www.mediawiki.org [2]. [1] http://svn.wikimedia.org/viewvc/mediawiki/?view=rev&rev=41652 [2] http://www.mediawiki.org/wiki/API:Edit_-_Protect _______________________________________________ Mediawiki-api-announce mailing list Mediawiki-api-announce(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce

1 0

search article by geotag
by Xu ZiZhan 02 Oct '08

02 Oct '08

Hello, i saw that wikipedia articles are geotagted usint the template {{coord}},so can I search for a certain article by it's geotag? i have a certain coordinate,like latitude=37,longitude=-122,then I want to search articles in wikipedia "nearby" this coordinate,just like http://geonames.edesign.no/examples/nearbywikipedia I don't know how to do that . Any tips/answers are highly appreciated. Thanks.

2 1

GPS/GEO API
by Kevin Yang 02 Oct '08

02 Oct '08

Hello , i am trying to develop a mobile wikipedia product which utilize the GPS data. I noticed that google maps have a button "more -> wikipedia" which will show wikipedia articles near a specific location . I am curious how that works? Any tips/answers are highly appreciated. Thanks.

3 2

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Mediawiki-api October 2008