Page MenuHomePhabricator

Large files uploaded with UploadWizard fail to post file information
Open, MediumPublicBUG REPORT

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptFeb 7 2020, 2:22 AM
Reedy added a subscriber: Reedy.Feb 7 2020, 4:17 AM

Any idea how they're being uploaded? Special:Upload, UploadWizard, some other tool?

Do we know if they're actually putting a description on it?

Aklapper changed the task status from Open to Stalled.Feb 7 2020, 1:07 PM

Steps to Reproduce: Upload a very large image.

Please provide clearer steps that leave no room for interpretation about websites, tools used, at which step happens what, etc., as a list.
See https://www.mediawiki.org/wiki/How_to_report_a_bug - thanks!

The files were uploaded with UploadWizard
12:11, 3 February 2020 Akhtar736 talk contribs uploaded File:Infected chillie or circumstances.jpg (User created page with UploadWizard)

Similar task exists since 2014 on GWToolset board T73527 with no solution.

@Aklapper @Reedy

Sorry I wasn't subscribed or I missed the emails.

In all the examples the user used the upload wizard. They are all users from countries whose first language is not English (standard disclaimer that correlation != causation). It only occurs with very large files (~10MB+).

This guy has a habit of uploading very high resolution photos which post empty.

There were two uploads today in English from the US, so it probably isn't a language issue.

Aklapper renamed this task from Large files are failing to post file information to Large files uploaded with UploadWizard fail to post file information.Apr 10 2020, 7:06 PM
Aklapper changed the task status from Stalled to Open.
MarkTraceur triaged this task as Medium priority.Jul 6 2020, 4:12 PM
MarkTraceur added a subscriber: MarkTraceur.

Marking as medium to note that this is probably something someone should investigate, but n.b. that work on UploadWizard is not generally a priority for anyone - and after a brief poke around Special:NewFiles, I couldn't find any instances of this happening right now, so I suspect it may be a fairly specific problem which may require additional information (what browser(s) are being used? what versions? what kinds of information did they *try* to input?)

Anyway, thanks for the report, even if it's taken a while to triage and may take longer to actually handle :)