Page MenuHomePhabricator

Skip page creation log for new file description pages on upload
Open, LowPublicFeature

Description

Feature summary (what you would like to be able to do and where):

[...]
As such, perhaps it would make sense to codify that in MediaWiki natively that for NS_FILE we don't emit this event and instead assume it to be an upload (manually created pages there are very rare and usually an accident, and for catching/reviewing that we have recent changes already).

Would it be possible to only log filespace creations not associated with uploads? From a user's perspective, this wouldn't be too unexpected, as Special:Newpages already does that in the file namespace.

Use case(s) (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution):
Reduce needed logging volume

Benefits (why should this be implemented?):
Allows to enable the feature on commons

Description from T198627:
When a file such as File:Barossa Rams logo.png is uploaded, log entries are generated in both the upload and creation logs. The creation log entry, however, is redundant to the upload log entry, so only an upload entry should be generated when uploading a new file. We could also create a maintenance script that deletes creation log entries that duplicate upload log entries.

Event Timeline

Change 718527 had a related patch set uploaded (by Umherirrender; author: Umherirrender):

[mediawiki/core@master] Skip page creation log for new file description pages on upload

https://gerrit.wikimedia.org/r/718527

After this is implemented, one should then create a maintenance script that deletes creation log entries that duplicate upload log entries (as I have originally stated at T198627, which has been merged here). Also, redundant page creation log entries should likewise not be generated when creating a page with a non-default content model, since the same information is already shown at Special:Log/contentmodel.

Umherirrender triaged this task as Low priority.