Mediawiki-api

mediawiki-api@lists.wikimedia.org

1262 discussions

Tips for using bots and user scripts with Flow
by Matthew Flaschen 29 Sep '15

29 Sep '15

Flow will start appearing more widely soon when we release a feature to allow users on certain wikis to opt into Flow on their user talk pages. The most common thing you'll probably want to do on a Flow page is post a new topic. For Pywikibot, that is pretty easy, since they have Flow support now. See https://www.mediawiki.org/wiki/Manual:Pywikibot/Flow . For on-wiki scripts, you can use MessagePoster (you don't need to know if it's a Flow board ahead of time!): --- var title = new mw.Title( 'titleString' ); var posterPromise = mw.messagePoster.factory.create( title ); posterPromise.done( function ( poster ) { poster.post( 'This is the topic title', 'This is the body of a message posted with MessagePoster' ); } ); --- Depend on 'mediawiki.messagePoster' and 'mediawiki.Title'. In some cases, you might want to check if a link is already there (e.g. to see if a warning template already included links to a particular policy). You can use prop=links for this. Flow is based on an infinitely-scrollable list of topics, each of which is its own page. So to use prop=links, you may need to loop through a set of recent enough topics (e.g. 25) then combine them into a prop=links request, e.g. https://www.mediawiki.org/w/api.php?action=query&titles=Topic:Sojpiv245cuiw… . pywikibot has support for looping through topics. Some bots need to check the header of a page for wikitext (e.g. a bot exclusion template). This can be done with view-header, but I don't think pywikibot has support for that yet (but it can be done directly). See https://www.mediawiki.org/w/api.php?action=flow&format=jsonfm&page=Talk%3AF… . A better way to do this would be templatelinks, but I'm not sure if there is an API to show templates PageX transcludes. For other questions, contact us at #wikimedia-collaboration . Or, if a certain tool needs Flow support and you're not sure where to start, you can file a bug (you can also reply here, but a ping in IRC would be appreciated). Matt Flaschen

1 0

How to expand only {{subst:}} and {{safesubst:}}
by Nicolas Vervelle 20 Sep '15

20 Sep '15

Hi, Is it possible through the API to give it some wikitext and get in return the same wikitext where {{subst:}} and {{safesubst:}} have been replaced, as they would be when saving an edit ? In WPCleaner <https://en.wikipedia.org/wiki/Wikipedia:WPCleaner>, I want to be able to insert things like current date, so I'm currently inserting things like {{safesubst:CURRENTMONTHNAME}} but as they don't work inside <ref> tags, I'd prefer to expand then myself rather than relying on the action=edit to do it. Nico

2 4

Re: [Mediawiki-api] How to expand only {{subst:}} and {{safesubst:}}
by billinghurst 19 Sep '15

19 Sep '15

Why not just make <ref> a tag ... {{subst:#tag:ref|{{safesubst:CURRENTMONTHNAME}}}} OR {{#tag:ref|{{safesubst:CURRENTMONTHNAME}}}} Regards, Billinghurst 1. How to expand only {{subst:}} and {{safesubst:}} > (Nicolas Vervelle) > > > > ---------- Forwarded message ---------- > From: Nicolas Vervelle <nvervelle(a)gmail.com> > To: List - MediawikiAPI <mediawiki-api(a)lists.wikimedia.org> > Cc: > Date: Sat, 19 Sep 2015 13:09:51 +0200 > Subject: [Mediawiki-api] How to expand only {{subst:}} and {{safesubst:}} > Hi, > > Is it possible through the API to give it some wikitext and get in return > the same wikitext where {{subst:}} and {{safesubst:}} have been replaced, > as they would be when saving an edit ? > > In WPCleaner <https://en.wikipedia.org/wiki/Wikipedia:WPCleaner>, I want > to be able to insert things like current date, so I'm currently inserting > things like {{safesubst:CURRENTMONTHNAME}} but as they don't work inside > <ref> tags, I'd prefer to expand then myself rather than relying on the > action=edit to do it. > > Nico > _______________________________________________ > Mediawiki-api mailing list > Mediawiki-api(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/mediawiki-api >

2 1

Query: Search API
by Chen Sung 02 Sep '15

02 Sep '15

Hi, I need to get a list of title, timestamp and wikipedia link of the items after doing a search. I tried using the “Search” API but it returns only title and timestamp not the wikipedia link. Can you please me in figuring out if a single API call will be enough for it or do I need to make calls to different API’s ? Please pardon me if I am missing something. Regards, Chen

1 0

Office Hour about mediawiki.org API pages Tuesday Sept 1
by S Page 28 Aug '15

28 Aug '15

Tuesday 2015-09-01T18:00 UTC [1] (11am San Francisco time) we will be having an IRC office hour [2] about the mw.org API: namespace. * As Wikimedia adds other APIs such as Wikidata Query Service and RESTBase, the structure and navigation needs to evolve. * Also, as you may know we are writing pages to encourage third-party developers to use Wikimedia data and APIs, and eventually want this "Web APIs hub" [3] to become the "front door" rather than API:Main_page. ** and presented with a different appearance to new developers [4] If you have thoughts, opinions, or needs from the API pages, I hope you can attend. The last bullet point is challenging and controversial, so it helps to share ideas and approaches. The Phab task https://phabricator.wikimedia.org/T110108 links to related tasks. It's also a Phab event https://phabricator.wikimedia.org/E50 and on the internal WMF Engineering calendar. See you in irc:freenode.net#wikimedia-office [1] http://www.timeanddate.com/worldclock/fixedtime.html?hour=18&min=00&sec=0&d… [2] https://meta.wikimedia.org/wiki/IRC_office_hours#Upcoming_office_hours [3] https://www.mediawiki.org/wiki/API:Web_APIs_hub [4] http://devhub.wmflabs.org/wiki/API:Web_APIs_hub -- =S Page WMF Tech writer, and Quim Gil Engineering Community manager

1 0

get wiki content from api
by ArtGiray . 28 Aug '15

28 Aug '15

What is the difference of this two queries? https://en.wikipedia.org/wiki/Car?action=raw https://en.wikipedia.org/w/index.php?title=Car&action=raw (i used first one before, then use second, but sometimes it's not response...) are any of these queries doing extra processing on server side ? which one i should use for more speed on my wikibot? (or any different query suggestion?)

3 2

[Mediawiki-api-announce] Wikidata API breaking changes
by Addshore 27 Aug '15

27 Aug '15

Hi all! We have some breaking API changes that will soon be deployed to wikidata.org. The deployment date should be: 9th September 2015 (just under 2 weeks) The change making the breaks an be found at: https://gerrit.wikimedia.org/r/#/c/227686/ The breaking changes are: - XML output aliases are now grouped by language - XML output may no longer give elements when they are empty - XML any claim, qualifier, reference or snak elements that had an '_idx' element will no longer have it - ALL output may now give empty elements, ie. labels when an entity has none If you want to see a wikipage explaining these changes take a look at: https://www.wikidata.org/wiki/User:Addshore/API_Break_September_2015 If you have any questions regarding these breaking changes please ask! Addshore _______________________________________________ Mediawiki-api-announce mailing list Mediawiki-api-announce(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce

1 0

Extension:Proofreadpage edit
by Zenon Panoussis 24 Aug '15

24 Aug '15

Hello all I am using the Proofreadpage extension to create a wiki of old Greek legislation. I can upload the images and unproofed texts and create all the Page: pages with mwclient, but I can for the life of me not figure how to create the Index: pages with properly filled-in form fields with the API. Example here: http://textarchives.gr/wiki/index.php?title=Index:Fek-1997-a-0260.pdf&actio… (please don't save the page, or else the sample form will vanish). Creating and saving the page is not a problem. The problem is how to fill in the form fields before saving. Does anyone know how to do this or have a pointer to something that might get me on the right track? Z

2 2

Search page content without download the page?
by ArtGiray . 17 Aug '15

17 Aug '15

Hi, For example a want to search "a+b+c" regex word in 1.000.000 page content. I can get all page content (this mean i download the page content to my pc) from api and search it. But i don't want to download 1.000.000 pages to my pc (because it is very lazy search and too many bandwidth for me and for wikipedia), i just want search a word from the server side? Is it possible to search page content from server side and if page contain my words then i get it's title? i want like this query: https://en.wikipedia.org/w/api.php?action=query&type=iscontainword&regexwor…

3 9

Re: [Mediawiki-api] [Wikitech-l] Bikeshedding a good name for "the api.php API"
by S Page 10 Aug '15

10 Aug '15

tl;dr: "PHP action API" I'm organizing content in the mediawiki.org API namespace, https://phabricator.wikimedia.org/T105133 , and so back to this bikeshed from August 2014. We do now have the extra APIs. https://en.wikipedia.org/api/ names them * PHP action API * REST content API I don't know who came up with the first name. I like it, it straddles Brad Jorsch's > seems like "action API" and "api.php" are the two contenders. I'm changing the API navigation accordingly, https://www.mediawiki.org/wiki/Template:API but the shed isn't going anywhere :) FWIW in writing documentation, I've found "the core API" is misleading because extensions add API modules to it. Is Wikidata part of "the core API" when only one wiki implements all its wbXXX modules? A lot of API clients rely on the extracts and pageimages modules, but they're not part of core. Cheers, >>>> it was twelve months ago... >>>> On Fri, Aug 15, 2014 at 10:00 AM, Tyler Romeo <tylerromeo(a)gmail.com> wrote: > Agreed with Aaron. When these proposed additional APIs are actually > implemented, then we can start arguing about what to call them. > > I know that I personally will continue to call the API the “core web API” > or sometimes just the “web API”, if it is clear based on the context in > which I am talking. > -- > Tyler Romeo > 0x405D34A7C86B42DF > > From: Aaron Halfaker <ahalfaker(a)wikimedia.org> > Cc: MediaWiki API announcements & discussion < > mediawiki-api(a)lists.wikimedia.org>> > Subject: Re: [Wikitech-l] [Mediawiki-api] Bikeshedding a good name for > "the api.php API" > > As a heavy user, I generally just refer to the things api.php does as "the > API". or "MediaWiki's web API" when I'm feeling verbose. > > I'd be confused about the "action API" since I generally use it to "read" > which isn't really "action" -- even though it corresponds to "action=query" > > As for "the proposed REST API", I don't think that proposed things should > affect the naming scheme of things we already know and love. > > Also, I think that all bike sheds should match the color of the house to > (1) denote whose bike shed it is and (2) help tie the yard together like > furniture in a living room. > > > On Fri, Aug 15, 2014 at 3:50 PM, Sumana Harihareswara < > sumanah(a)wikimedia.org > > wrote: > > > I like "action API". > > > > Sumana Harihareswara > > Senior Technical Writer > > Wikimedia Foundation > > > > > > On Thu, Aug 14, 2014 at 5:06 PM, Brad Jorsch (Anomie) < > > bjorsch(a)wikimedia.org > > > wrote: > > > > > Summing up, it seems like "action API" and "api.php" are the two > > > contenders. > > > > > > "api.php" is least likely to be confused with anything (only its own > > entry > > > point file). But as a name it's somewhat awkward. > > > > > > "action API" might be confused with the Action class and its > subclasses, > > > although that doesn't seem like a big deal. > > > > > > > > > As for the rest: > > > > > > Just "API" is already causing confusion. Although it'll certainly > > continue > > > to be used in many contexts. > > > > > > "MediaWiki API", "Web API", and "MediaWiki web API" are liable to be > > > confused with the proposed REST API, which is also supposed to be > > > web-accessible and will theoretically part of MediaWiki (even though > I'd > > > guess it's probably going to be implemented as an -oid). "MediaWiki web > > > APIs" may well grow to encompass the api.php action API, the REST API, > > and > > > maybe even stuff like Parsoid. > > > > > > "MediaWiki API" and "Core API" are liable to be confused with the > various > > > hooks and PHP classes used by extensions. > > > > > > "JSON API" wouldn't be accurate for well into the future, and would > > likely > > > be confused with other JSON-returning APIs such as Parsoid and maybe > > REST. > > > > > > "Classic API" makes it sound like there's a full replacement. > > > > > > All the code name suggestions would be making things less clear, not > > more. > > > If it had started out with a code name there would be historical > inertia, > > > but using a code name now would just be silly. > -- =S Page WMF Tech writer

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Mediawiki-api