Last modified: 2013-01-02 11:10:08 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T19293, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 17293 - Allow Special:Log to be filtered by one or more log_type's and log_action's (checkboxes)
Allow Special:Log to be filtered by one or more log_type's and log_action's (...
Status: NEW
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on: 11739 18954
Blocks:
  Show dependency treegraph
 
Reported: 2009-01-31 22:14 UTC by Happy-melon
Modified: 2013-01-02 11:10 UTC (History)
2 users (show)

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


Attachments

Description Happy-melon 2009-01-31 22:14:35 UTC
This has been suggested before, and even an inverse filter raised significant performance concerns (bug 11739).  However, the benefit of having a checkbox-type system to select which log types to include would be great. Is this at all possible?
Comment 1 Krinkle 2013-01-02 11:09:33 UTC
Being able to query one specific action from a log type required a big index to be added (bug 18954), but that was done (SpecialPage UI hasn't been implemented yet, API interface is working, see bug 18954 commet 8).

Being able to filter by more than 1 type or action is more complicated, not sure if that is possible on the live cluster with a generic index on such a big dataset.

Currently it would get results by order of type/action first, not by timestamp. And given the large number of log actions, filtering type A, B and C with limit to 50 results would only yield 50 results of A.

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


Navigation
Links