[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Page MenuHomePhabricator

Create "filemove" log action within log type "move" (since 'movefile' is a separate right now)
Open, MediumPublicFeature

Description

Author: RSYQFIOJGWZA

Description:
The filemover capability was implemented pursuant to bug T25488, but there is no easy way to track the filemoves made by the filemover group (or by others with the filemover right).

This could also be accomplished by adding a file namespace filter to the move log on Commons, but that was expensive 2008-07-03 per bug T16711#193349.

If there is consensus for a filemover capability on English Wikipedia (the discussion at http://en.wikipedia.org/wiki/Wikipedia:Village_pump_(proposals)#Transferring_over_.22filemover.22_tool is currently leaning in that direction), such a log would be helpful there, too.


Version: unspecified
Severity: enhancement
URL: http://commons.wikimedia.org/wiki/Commons:File_renaming#Is_there_a_log_of_file_renames.3F

Details

Reference
bz27709

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 11:34 PM
bzimport set Reference to bz27709.
bzimport added a subscriber: Unknown Object (MLST).

Wouldn't filtering the move log (or any other logs) at enwiki be precisely what [[bugzilla:14711]] is addressing? Is this also another request, or is this just for Wikimedia Commons?

RSYQFIOJGWZA wrote:

This is just for Wikimedia Commons (and now for English Wikipedia), as a namespace filter appeared not to be an option for them as of nearly three years ago. The filemover capability at English Wikipedia was implemented at bug 27927. The attempt to get a filemover capability at Test Wikipedia http://test.wikipedia.org/wiki/Talk:Main_Page#File_movers_group (to allow testwiki to better reflect the current state of English Wikipedia) has sadly had no responses yet. :(

Changing bug summary to reflect request.

Since "movefile" is a seperate user right, I think this is (by exception) not a duplicate of bug 14711.

Changing the bug summary to account for this (it's not specific to the English Wikipedia or Wikimedia Commons)

  • This bug has been marked as a duplicate of bug 14711 ***

This is just for Wikimedia Commons (and now for English Wikipedia), as a
namespace filter appeared not to be an option for them as of nearly three years
ago.

Changing the bug summary to account for this (it's not specific to the English
Wikipedia or Wikimedia Commons)

Which one is it? Is it restricted to a certain class of users/userrights or a certain set of Wikimedia wikis? All sysops have movefile rights; does that mean we should attach the filemover log on all sysops on all Wikimedia wikis as well?

(In reply to comment #5)

(In reply to comment #2)

This is just for Wikimedia Commons (and now for English Wikipedia), as a

namespace filter appeared not to be an option for them as of nearly three years
ago.

(In reply to comment #4)

Changing the bug summary to account for this (it's not specific to the English
Wikipedia or Wikimedia Commons)

Which one is it? Is it restricted to a certain class of users/userrights or a
certain set of Wikimedia wikis? All sysops have movefile rights; does that mean
we should attach the filemover log on all sysops on all Wikimedia wikis as
well?

Well, the way I see it there's three options:

  • Hack something very ugly specifically for Wikimedia's usergroup "filemover" which will only log the "movefile" action for that user group (and not if done by sysops). This is either impossible from the setting or it maybe as some kind of extension, seems a little overkill to me.
  • Seperate the "movefile" log action from the general "move" action (this is already done as of 1.17) so that the different actions within that "move" log_type can be filtered (bug 18954)
  • Assume that every move in the File-namespace is a file move and use the namespace filter (bug 14711) to do this. This implementation is not water tight as there can be pages without media in the File-namespace (ie. local description pages, temporary placeholders or vandalism), although it's not a huge deal, there are better ways.

So all those considered, I think the second one seems the best option here.

Are we still going to work on this?

In T29709#2026320, @Pokefan95 wrote:

Are we still going to work on this?

If "we" means you: Your patch is very welcome. :) See https://www.mediawiki.org/wiki/Developer_access

In T29709#2026320, @Pokefan95 wrote:

Are we still going to work on this?

If "we" means you: Your patch is very welcome. :) See https://www.mediawiki.org/wiki/Developer_access

Commons hasn't a lot of tech users. Can staff fix this task? :-) Would be kind.

So, is anyone working on this or what is happening :-) Think it has been sitting here for some time now.

Nobody is assigned to this task and there are no recent patches. Hence: No, nobody is working on this.

Aklapper changed the subtype of this task from "Task" to "Feature Request".Feb 4 2022, 12:24 PM