API talk:Revisions

sizediff
API:Usercontribs includes  in its. Why doesn't this module include the same? --2601:140:8980:FE0:50B8:7ADD:EA94:2B6B 14:47, 7 March 2018 (UTC)

Userhidden
Need to explain " " and " " a bit more. See also API_talk:Database_field_and_API_property_associations. « Saper // talk » 17:05, 27 May 2015 (UTC)
 * Yeah, that would be usefull. --jobu0101 (talk) 09:06, 4 March 2016 (UTC)
 * Not sure where to put it, but the  flag is true when a revision has been revision-deleted and the user's name has been removed as part of that. The   flag simply flags a revision as having been done by an IP user. I'm not sure if this is even possible, but I suppose it would help to distinguish between a user who chooses the name "1.2.3.4" as compared to someone editing from the IP address "1.2.3.4". – Robin Hood   (talk)  21:43, 4 March 2016 (UTC)

FlaggedRevs
Can I have revision history with id's of user, which have reviewed every revision. Malarz pl (talk) 09:59, 13 April 2016 (UTC)
 * I'm not sure if this is possible or not, as I have no experience with FlaggedRevs, but you might want to have a look at their API docs and see if anything there helps. If not, I'd suggest asking on that talk page rather than this one, as you're more likely to find people who have the experience to answer your question. – Robin Hood  (talk)  21:43, 13 April 2016 (UTC)
 * Thanks. I alreaeady asked there. Malarz pl (talk) 06:29, 14 April 2016 (UTC)
 * And I added infromation to this page. Malarz pl (talk) 06:52, 14 April 2016 (UTC)
 * Sorry, I just removed that same info. Generally speaking, info for various extensions, even those used by MediaWiki sites, are only documented on the extension's page. I don't know if there's ever been a formal discussion about that, though, so if you want to bring it to somewhere like the Community Portal or wherever, I'm certainly open to discussing/changing that policy. – Robin Hood  (talk)  07:46, 14 April 2016 (UTC)

Deprecated parameters
Hello, I just noticed these warnings when running some ajax script: The parameter "rvdifftotext" has been deprecated. The parameter "rvdifftotextpst" has been deprecated. Indeed, there has been a bunch of deprecations: T164106 Deprecate parsing and diff options in ApiQueryRevisionsBase. The documentation of this page should be updated accordingly.

Od1n (talk) 06:35, 29 December 2017 (UTC)
 * Exhaustive list, from the Gerrit changeset: "The 'rvdifftotext', 'rvdifftotextpst', 'rvdiffto', 'rvexpandtemplates', 'rvgeneratexml', 'rvparse', and 'rvprop=parsetree' parameters to prop=revisions are deprecated, as are the similarly named parameters to prop=deletedrevisions, list=allrevisions, and list=alldeletedrevisions. Use action=compare, action=parse, or action=expandtemplates instead."
 * Od1n (talk) 06:38, 29 December 2017 (UTC)
 * All done - Special:Diff/2673288 (API:Alldeletedrevisions), Special:Diff/2673287 (API:Allrevisions), Special:Diff/2673286 (API:Deletedrevisions), and Special:Diff/2673285 (API:Revisions). SamanthaNguyen (talk) 19:30, 29 December 2017 (UTC)

rvslots & rvprop
Hello,

When I use the revisions API with the rvprop parameter, I get the following warning: Because "rvslots" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used See the following request, for example: |tags.

It seems that "rvslots" isn't documented on this page. How should this parameter be used?

Thanks!

109.10.228.105 08:27, 3 August 2018 (UTC)


 * This is the first I'm hearing of it myself, because I don't have the time/energy to keep up on every last change the MW team makes, but this seems to be a fairly major change to the MediaWiki architecture called "Multi-Content Revisions". Right now, it only even exists in the WMF beta builds, it's not in the 1.31 release. High-level documentation about MCR is here. The gist of it seems to be that instead of storing just a single text block for any given revision, data could be separated out into different "slots" which represent different aspects of the data. For example, infoboxes could be stored in one slot, separate from the main content of a revision; template parameters could become part of the metadata for a template rather than relying on only human-readable documentation (I gather this sort of exists on MW already via JSON data, but I'm not sure of the specifics); even the regular page content could be separated into different types of data, if appropriate. One might even be able to use this to store multi-language content in a less kludgey way, though I'm not sure if that's something that's really on the drawing board at this point.


 * Being such a large change, I think it's best to continue doing things the old way for now, and wait for the MCR team to provide full documentation. – Robin Hood  (talk)  21:20, 3 August 2018 (UTC)