Last modified: 2008-01-28 13:58:24 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 12816 - API function to return random page(s) in selected namespace(s)
API function to return random page(s) in selected namespace(s)
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
API (Other open bugs)
1.12.x
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-01-28 10:21 UTC by OverlordQ
Modified: 2008-01-28 13:58 UTC (History)
1 user (show)

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


Attachments
ApiQueryRandom (3.76 KB, application/octet-stream)
2008-01-28 10:21 UTC, OverlordQ
Details
Patch to add it to the API (1.10 KB, patch)
2008-01-28 10:22 UTC, OverlordQ
Details

Description OverlordQ 2008-01-28 10:21:26 UTC
Created attachment 4592 [details]
ApiQueryRandom

Basically add the functionality of Special:Random to the API with the addition of a parameter to return more then one result.

I've (tried) to create a working implementation but I'm sure my lack in knowledge of WP internals severely screwed it up. I'll
Comment 1 OverlordQ 2008-01-28 10:22:43 UTC
Created attachment 4593 [details]
Patch to add it to the API
Comment 2 Roan Kattouw 2008-01-28 13:58:24 UTC
Added in r30217.

(In reply to comment #0)
> I've (tried) to create a working implementation but I'm sure my lack in
> knowledge of WP internals severely screwed it up.
Your patch contained some duplicate code and only listed redirects (page_is_redirect != 0 rather than = 0), but I've seen far worse.



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


Navigation
Links