UploadWizard unable to recover from warnings
OpenPublic

Description

Author: davidrichfield

Description:
When I try to upload an svg version of a file that is already on commons, the new "same name" detection completely prevents me from uploading it. This restriction needs to be relaxed.


Version: master
Severity: major
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=59203
https://bugzilla.wikimedia.org/show_bug.cgi?id=70617

bzimport set Reference to bz46741.
bzimport created this task.Via LegacyMar 31 2013, 7:39 PM
Aklapper added a comment.Via ConduitApr 2 2013, 8:39 AM

Hi, did you use http://commons.wikimedia.org/wiki/Special:UploadWizard or http://commons.wikimedia.org/wiki/Special:Upload for uploading? (It's always highly welcome to provide exact steps to reproduce, in order to avoid ambiguity.)

What would be good reasons to relax that restriction? If you automatically convert from e.g. svg to png you'd run into filename collisions.

bzimport added a comment.Via ConduitApr 3 2013, 7:25 PM

davidrichfield wrote:

I got there from [[Special:Upload]] - specifically by typing the required filename into the address bar and clicking on "upload"

The reason to relax the restriction is that we often create svg diagrams based on other filetypes (most often .jpg, .gif and .png) - very many national flags, scientific diagrams and charts are made that way: an initial uploader supplies a file in a non-vector format, which is then transformed (often after a request at [[:en:WP:GL/I]]) to an SVG file. Both files still need to be kept (at least for a while): at first they need to be compared to make sure that the vector diagram is a faithful rendition, and sometimes later a PNG version is made offline in Inkscape because the automatic PNG versions (made with librsvg) don't render faithfully. See for example [[:File:Steroidogenesis.svg]] and [[:File:Steroidogenesis.png]]. They coexist without problems. Under what circumstances would a name collision occur? All the preview images are prefixed with "(number)px-"

I'm also not the only one to see this problem. See for example the discussions at http://commons.wikimedia.org/wiki/Commons:Forum#Upload_gleicher_Name and http://commons.wikimedia.org/wiki/Commons:Help_desk#Can.27t_upload_an_SVG_version_of_a_PNG

McZusatz added a comment.Via ConduitApr 10 2013, 5:20 PM

Would be nice to know why this was introduced (and when)... Nevertheless it 'could' be useful considering it was possible to upload files like:
*movie.ogv
*movie.webm
*movie.ogg
containing all the same content.

(In reply to comment #1)

Hi, did you use http://commons.wikimedia.org/wiki/Special:UploadWizard or
http://commons.wikimedia.org/wiki/Special:Upload for uploading? (It's always
highly welcome to provide exact steps to reproduce, in order to avoid
ambiguity.)

What would be good reasons to relax that restriction? If you automatically
convert from e.g. svg to png you'd run into filename collisions.

Both are affected (UpWiz and old upload form)

(In reply to comment #2)
Clumsy workaround: You can still upload the file to any random name and move it directly after upload to the wanted name.

Bawolff added a comment.Via ConduitMay 10 2013, 1:27 AM

Seems to be introduced in I21eddc5d08ca3c23b3 / bug 40326

Bawolff added a comment.Via ConduitMay 10 2013, 1:31 AM

(In reply to comment #4)

Seems to be introduced in I21eddc5d08ca3c23b3 / bug 40326

It seems to me that this should be a "recoverable warning" (By which I mean you ask the user if they are sure, and then let them do it if they really want to). Does that sound right?

bzimport added a comment.Via ConduitMay 10 2013, 10:30 AM

davidrichfield wrote:

That would solve my problem, and I guess it would still avoid the problem in Bug 40326.

This would also allow a user to make an intelligent choice, for example if I want to upload steroidogenesis.svg and there's already a steroidogenesis.png, I can either keep the filename if I'm just making an svg version of the png, or change the name if it's a completely different picture.

Rillke added a comment.Via ConduitMay 28 2013, 10:57 AM

(In reply to comment #5)

this should be a "recoverable warning"

Recoverable only if it has a different file extension/type. Uploading Foo.JPG and Foo.jpg should be still impossible (as some file systems do not like this; Just imagine, their MD5 would start with the same byte).

bzimport added a comment.Via ConduitMay 28 2013, 10:54 PM

kevjonesin wrote:

Recoverable with a different file extension/type sounds good to me.

I'd recently added transparent backgrounds (alpha channels) to some .jpg images via [[GIMP]] and was a bit irked/befuddled when I'd entered info for multiple .png versions I was uploading simultaneously via UploadWizard only to get denied at the end. At the very least it would be nice if the filename denial had come nearer the start of the process. Of course a "recoverable warning" would make this moot... well, perhaps not... it would still be nice to get warnings regarding filenames as soon as the file name is entered via the file browser. Before going through additional steps.

Advance 'tanx' goes out to those with the skillz, : }

bzimport added a comment.Via ConduitMay 28 2013, 10:59 PM

kevjonesin wrote:

p.s. I'm...
[[User:Kevjonesin|Kevjonesin]] ([[User talk:Kevjonesin|talk]]) 22:58, 28 May 2013 (UTC)
...on English Wikipedia.

Aklapper added a comment.Via ConduitMay 29 2013, 12:09 PM

Bryan.TongMinh: Could you take a look at this, as https://gerrit.wikimedia.org/r/#/c/24124/ was written by you? Thanks.

McZusatz added a comment.Via ConduitJun 20 2013, 6:37 PM

Please fix this bug or revert the initial commit. This should not stay the way it is now.
FYI: I wasted some hours with debugging some python script because I could not upload a WebM file. Some minutes ago I realized another file was already uploaded with the same name (totally unrelated) with PNG extension.

Even if there are two related files like "animal123.png" & "animal123.webm" the error should not show up!

Bawolff added a comment.Via ConduitNov 7 2013, 4:29 AM

Is this still an issue on commons. (I was going to review your commit [Sorry about letting that fall through the cracks] today), but I couldn't reproduce the issue locally. Although it may be me just getting a little sleepy and doing something stupid

McZusatz added a comment.Via ConduitNov 7 2013, 5:30 PM

(In reply to comment #12)

Is this still an issue on commons?

Jup!

McZusatz added a comment.Via ConduitNov 8 2013, 10:07 AM

Related Patch set:
Change 87020
Change-Id I1a98bf43284b5045b1ee6c60e64075404fd0a837

https://gerrit.wikimedia.org/r/#/c/87020/

Bawolff added a comment.Via ConduitNov 15 2013, 6:25 PM

(In reply to comment #13)

(In reply to comment #12)
> Is this still an issue on commons?
Jup!

Really, because I was able to successfully upload https://commons.wikimedia.org/wiki/File:Carngranny_level_crossing_-_geograph.org.uk_-_274643.png even though https://commons.wikimedia.org/wiki/File:Carngranny_level_crossing_-_geograph.org.uk_-_274643.jpg exists

McZusatz added a comment.Via ConduitNov 15 2013, 8:48 PM

It is not possible for me to use the UpWiz which gives me:

There is [/wiki/File:Carngranny_level_crossing_-_geograph.org.uk_-_274643.webm another file] already on the wiki with the same filename

in red textcolor regardless of me clicking on "Retry failed uploads".

Also youtube2mediawiki gives "Upload failed."

Bawolff added a comment.Via ConduitNov 15 2013, 8:50 PM

(In reply to comment #16)

It is not possible for me to use the UpWiz which gives me:

There is
[/wiki/File:Carngranny_level_crossing_-_geograph.org.uk_-_274643.webm
another file] already on the wiki with the same filename

in red textcolor regardless of me clicking on "Retry failed uploads".

Also youtube2mediawiki gives "Upload failed."

I would view that as an upload wizard bug in that it doesn't allow people to bypass warnings. It seems kind of silly to me to get rid of all non-critical warnings because upload wizard is not giving the option to the user to ignore them

McZusatz added a comment.Via ConduitNov 15 2013, 9:00 PM

(In reply to comment #17)
Makes sense, actually. I guess we better file a new bug as this one is quite stuffed?

Bawolff added a comment.Via ConduitNov 15 2013, 9:06 PM

(In reply to comment #18)

(In reply to comment #17)
Makes sense, actually. I guess we better file a new bug as this one is quite
stuffed?

Although it appears that originally this happened for Special:Upload too, We could probably just move this bug to uploadWizard component.

MarkTraceur added a comment.Via ConduitNov 15 2013, 10:10 PM

I guess we could add in a check to ignore the filename exists error if they're not actually identical - i.e. the extension is different. That sounds fine to me. As long as we warn the user in the description step.

McZusatz added a comment.Via ConduitDec 7 2013, 5:08 PM

Changing importance: This is not an "enhancement" but a major bug displeasing uploaders for months now.

Just two more examples:
https://commons.wikimedia.org/w/index.php?oldid=103108315
https://commons.wikimedia.org/w/index.php?diff=111356217

Aklapper added a comment.Via ConduitDec 9 2013, 12:23 PM
  • Bug 58186 has been marked as a duplicate of this bug. ***
Rillke added a comment.Via ConduitDec 18 2013, 7:27 PM

(In reply to comment #21)

I guess we could add in a check to ignore the filename exists error if they're
not actually identical - i.e. the extension is different. That sounds fine to
me. As long as we warn the user in the description step.

What would you like to "warn the user about"?

Aklapper added a comment.Via ConduitJan 2 2014, 10:48 AM

mtraceur: Could you answer comment 24 please?

MarkTraceur added a comment.Via ConduitJan 8 2014, 11:52 PM

Well, I would definitely like to tell the user that they're creating a potentially confusing filename. I won't make it *fatal*, but there should be notice of some sort.

Rillke added a comment.Via ConduitApr 16 2014, 10:19 PM

(In reply to Mark Holmquist from comment #26)

Any progress? Or can I author a patch?

McZusatz added a comment.Via ConduitApr 17 2014, 7:20 AM

(In reply to Rainer Rillke @commons.wikimedia from comment #27)
Please do. :)

Regardless whether you decide to include a warning or decide to drop them... Everything is better than the current state which blocks "valid" uploads and confuses uploaders.

AdamCuerden added a comment.Via ConduitJun 9 2014, 3:34 PM

This also causes problems with PNG/JPEG versions - JPEGs display better, but are lossy, so, with scans and restorations it's pretty normal to have both a JPEG and PNG. Up until recently, it was at least possible to upload both at once, it's blocked now.

AdamCuerden added a comment.Via ConduitJun 9 2014, 3:35 PM

(By which I mean that the recent patch actually made the uploads ''more'' restrictive.)

MarkTraceur added a comment.Via ConduitSep 10 2014, 8:25 PM

It looks like no work has been done on this, I'm going to try to whip up a patch now.

gerritbot added a comment.Via ConduitSep 10 2014, 10:31 PM

Change 159625 had a related patch set uploaded by MarkTraceur:
[WIP] Add override button back in

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

MarkTraceur added a comment.Via ConduitSep 11 2014, 4:03 PM

This is WIP because the issues with the prior patches still exists. I guess we need to finish refactoring before we can have any real solution here.

*weeping in the corner*

Gilles added a project: Multimedia.Via WebNov 24 2014, 3:11 PM
Gilles moved this task to Next up on the Multimedia workboard.Via WebDec 4 2014, 8:43 AM
Gilles moved this task to Current cycle on the Multimedia workboard.Via WebDec 10 2014, 5:43 PM
Lokal_Profil added a subscriber: Lokal_Profil.Via WebJan 21 2015, 5:23 PM
Gilles moved this task to Backlog on the Multimedia workboard.Via WebApr 6 2015, 9:22 AM
McZusatz added a comment.Via WebJul 11 2015, 9:50 PM

@all @MarkTraceur Is there any progress with doing the refactoring and then applying the patch?

Restricted Application added subscribers: Steinsplitter, Matanya. · View Herald TranscriptVia HeraldJul 11 2015, 9:50 PM
Aklapper added a comment.Via WebJul 26 2015, 8:43 AM

@MarkTraceur Is there any progress with doing the refactoring and then applying the patch?

McZusatz added a comment.Via WebJul 26 2015, 10:49 AM

If not, please add a blocking task for clarity.

Peachey88 removed a subscriber: Peachey88.Via WebJul 26 2015, 8:37 PM

Add Comment