The title says it all.
Version: 1.23.0
Severity: enhancement
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=25931
The title says it all.
Version: 1.23.0
Severity: enhancement
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=25931
Once there's a clear implementation path for this bug, it should be possible to mark it with the "easy" keyword.
So roughly what needs to be done here:
That's the status quo pattern, but long term this is not a pattern we want to preserve. We'd prefer to separate UI and backend functionality rather that having API modules call methods on special page classes.
In SpecialRandomInCategory.php:
The method used here is rather biased. It is assumed that the use of this page will be people wanting to get a random page out of a maintenance category, to fix it up. The method used by this page should return different pages in an unpredictable fashion which is hoped to be sufficient, even if some pages are selected more often than others.
A more unbiased method could be achieved by adding a cl_random field to the categorylinks table.
If the goal of the API is the latter, adding cl_random as an available parameter of cmsort to API:Categorymembers could be a solution.