Last modified: 2014-08-21 15:11:24 UTC
When a page is moved, the API exposes only the pageid of the newly created redirect, the pageid of the moved page is missing: I created a page called "Alter Titel", edited it, then renamed it to "Neuer Titel", and edited it again. When I query the API for all data (/api.php?action=query&list=watchlist&wlallrev=&wllimit=500&wlprop=ids|title|flags|user|userid|comment|parsedcomment|timestamp|sizes|notificationtimestamp|loginfo&format=json) I get (extracted the relevant part): {"type":"edit","ns":0,"title":"Neuer Titel","pageid":433,"revid":4297,"old_revid":4295,"userid":"1","user":"Schnark","minor":"","oldlen":8,"newlen":8,"timestamp":"2014-08-20T13:14:18Z","notificationtimestamp":"","comment":"Bearbeitung","parsedcomment":"Bearbeitung"}, {"type":"log","ns":0,"title":"Alter Titel","pageid":434,"revid":0,"old_revid":0,"userid":"1","user":"Schnark","oldlen":0,"newlen":0,"timestamp":"2014-08-20T13:13:58Z","notificationtimestamp":"","comment":"Umbenennung","parsedcomment":"Umbenennung","logid":3788,"logtype":"move","logaction":"move","move":{"new_ns":0,"new_title":"Neuer Titel"}}, {"type":"edit","ns":0,"title":"Alter Titel","pageid":433,"revid":4294,"old_revid":4293,"userid":"1","user":"Schnark","oldlen":8,"newlen":8,"timestamp":"2014-08-20T13:13:35Z","notificationtimestamp":"","comment":"Bearbeitung","parsedcomment":"Bearbeitung"}, {"type":"new","ns":0,"title":"Alter Titel","pageid":433,"revid":4293,"old_revid":0,"userid":"1","user":"Schnark","new":"","oldlen":0,"newlen":8,"timestamp":"2014-08-20T13:13:19Z","notificationtimestamp":"","comment":"Neuanlage","parsedcomment":"Neuanlage"} Note that the entry for the move has "pageid":434 (the pageid for the newly created redirect). The pageid 433 for the moved page is missing.
*** This bug has been marked as a duplicate of bug 68950 ***
Are the two bugs really duplicates? This one is talking about page IDs; bug 68950 is talking about revision IDs.
Oh, good point. Bug 68930 is the one about *page* ids. *** This bug has been marked as a duplicate of bug 68930 ***