Last modified: 2014-03-31 18:39:39 UTC
When querying blocks, I can use bkprop=timestamp|expiry|by. For querying pages protected against creation there is ptprop=timestamp|expiry|user. (Althogh "user" has a different meaning here as for blocks.) What about other protections? A similar approp=blahblah is unfortunately missing fram allpages, or at least it is heavily undocumented on http://www.mediawiki.org/wiki/API:Allpages. I was suggested to get expiration from query as action=query&titles=title|title1&prop=info&inprop=protection and mine the protection log for timestamp of beginning (and for the admin who protected, I suppose). I can do that if necessary, but is complicated for me, slow for the bot and results in a greater server load. Would be nice to handle blocks, protections and create-protections in similar way.
That is not possible at the moment, because the "page restrictions" table does not store that information. The "ipblocks" table and the "protected titles" table store information about the performer of that action and than you can query this information.
OK, then the category should be changed: this is no more an API bug, rather a database bug. :-) It should store for practical reasons written above.
I have create a new bug to track that, because without an own bug for category API the api part maybe is not implemented, after the database is changed.
Oh, I didn't think of that. Thank you!
Needs to use the log_search, see Gerrit change #105443
