Last modified: 2014-06-16 12:30:43 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 16816 - Log actions should support bot flag (e.g. to hide from Special:RecentChanges)
Log actions should support bot flag (e.g. to hide from Special:RecentChanges)
Status: REOPENED
Product: MediaWiki
Classification: Unclassified
Recent changes (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-12-27 22:07 UTC by MZMcBride
Modified: 2014-06-16 12:30 UTC (History)
5 users (show)

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


Attachments

Description MZMcBride 2008-12-27 22:07:20 UTC
It should be possible to mark actions like delete and protect as bot (to avoid clogging RecentChanges) if a user has the 'markbotedit' right. This is probably custom enough that it needs to only be implemented in the API.
Comment 1 Mike.lifeguard 2008-12-28 05:58:04 UTC
(In reply to comment #0)
> It should be possible to mark actions like delete and protect as bot (to avoid
> clogging RecentChanges) if a user has the 'markbotedit' right. This is probably
> custom enough that it needs to only be implemented in the API.
> 

Why would it be the markbotedit right as opposed to the bot right? Not sure whether both would make more sense, but certainly bots making these actions should be hidden, if that's not already the case.
Comment 2 charitwo 2008-12-28 05:59:57 UTC
(In reply to comment #1)
> (In reply to comment #0)
> > It should be possible to mark actions like delete and protect as bot (to avoid
> > clogging RecentChanges) if a user has the 'markbotedit' right. This is probably
> > custom enough that it needs to only be implemented in the API.
> > 
> 
> Why would it be the markbotedit right as opposed to the bot right? Not sure
> whether both would make more sense, but certainly bots making these actions
> should be hidden, if that's not already the case.
> 

Yeah, any action performed by a bot, both edits and entries made to Special:Log are hidden from recent changes.
Comment 3 Alex Z. 2009-01-12 19:27:50 UTC
Using both the normal UI and the API, logged entries seem to be getting the bot flag when done by a flagged bot (a user with the "bot" right). 

I didn't test everything (tested delete, undelete, protect through normal UI; delete, move through API), if something isn't checking for the bot flag, this can be reopened. 

I don't think this should be expanded to the "markbotedit" right, as that's currently just used to hide mass rollbacks by admins.
Comment 4 MZMcBride 2009-01-12 22:35:37 UTC
Reopening. The goal here is to be able to mark actions as bot without being in the bot group. Ideally, this would be implemented into the API first and then subsequently implemented in the interface later (sort of like 'move without redirect'). Probably would be best to have a new right "markbotaction".
Comment 5 Roan Kattouw 2009-01-12 22:43:53 UTC
(In reply to comment #4)
> Ideally, this would be implemented into the API first and then
> subsequently implemented in the interface later (sort of like 'move without
> redirect'). Probably would be best to have a new right "markbotaction".
> 

It should be implemented in the *backend* first. When that's done, it's quite simple to update the API and UI to pass a $markBot parameter to the backend function and add a parameter (API) or checkbox (UI) to toggle it.

Through my work with the write API I've become familiar with some of the backend functions concerned, but I've got better things (i.e. API stuff) to do at the moment. I'll take this if no one else does, but the API has a higher priority for me, so it might take me a while to get to it. In the meantime, it would of course be nice if someone else took this bug.
Comment 6 Siebrand Mazeland 2009-02-02 13:32:39 UTC
Changed component to "RecentChanges"
Comment 7 Andre Klapper 2014-06-06 09:52:50 UTC
charitwo: Do you plan to work on a patch (or are you aware of somebody working on a patch), or why did you set the Target Milestone to 1.24?

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


Navigation
Links