Last modified: 2013-01-13 23:33:07 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 43943 - CheckUser API list=checkuserlog query does not contain a query-continue element
CheckUser API list=checkuserlog query does not contain a query-continue element
Status: RESOLVED DUPLICATE of bug 40658
Product: MediaWiki extensions
Classification: Unclassified
CheckUser (Other open bugs)
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2013-01-13 23:31 UTC by Hersfold
Modified: 2013-01-13 23:33 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Hersfold 2013-01-13 23:31:40 UTC
When using the API to access CheckUser logs[1], the results returned by the API do not provide a "query-continue" parameter as other query calls do[2]. This element is important for programs attempting to access this information, as it a) informs the program that there are still log entries fitting the specified criteria and thus another query needs to be run and b) prevents the retrieval of the same log entry twice by ensuring that subsequent queries continue where the previous one left off. Please ensure that the CheckUser API provides this information. Thanks!

[1]: (must be logged into an checkuser account)
Comment 1 Kunal Mehta (Legoktm) 2013-01-13 23:33:07 UTC

*** This bug has been marked as a duplicate of bug 40658 ***

Note You need to log in before you can comment on or make changes to this bug.