https://bugzilla.wikimedia.org/show_bug.cgi?id=29594
Erik Moeller <e...@wikimedia.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|High |Normal
CC| |e...@wikimedia.org
--- Comment #3 from Erik Moeller <e...@wikimedia.org> 2011-09-07 08:04:34 UTC
---
There are two separate issues described in this bug, which possibly should be
split into two bugs.
1) Making it more intuitive to start over when a batch is unsuccessful.
Currently, the only way to do so is to manually remove the files from the batch
(by mousing over them and clicking "remove"). I would suggest a "Start over"
button or something similar when a batch has errors, which would have the same
effect as removing all files individually.
2) Making it possible to override additional error conditions. Yes, this is
possible in the old form, although the UI and workflow is pretty horrible (your
file may have multiple error conditions, and you may have to go through
multiple submits, and discover the "Ignore warnings and save anyway", to
finally be able to push it through).
Saibo, to be clear about the different checks: UploadWizard already handles
filename conflicts very gracefully most of the time. Because of the way files
are stored in the stash, title issues don't have to be resolved until the
"Describe" step, at which point interactive JavaScript gives you hints about
needed renames. There's bug 30646, but other than that, I believe files should
never fail on the first step for title reasons.
The checks you're describing check the actual _contents_ of the file. So we're
talking about a use case where you can override the _exact same file_ that's
been previously deleted, or that exists in another copy.
I agree that it should be possible to override "previously deleted" files.
While blocking such files may have some vandalism fighting benefits, it's
fundamentally not very user-friendly, and as your link proves, it may cause
unrecoverable issues for users.
I am not sure I see the use case for overriding "duplicate content" files. Can
you give a real world example where that would actually be desirable?
As for the override UI: One reasonably (although not perfectly) discoverable
mechanism to do per-file overrides might be to have an "Upload anyway" button
next to the "Remove" link that appears on mouseover per file, which would act
as an instant resolution (turning from "Warning" to "OK") for that upload.
Reducing importance to "normal" for now as neither issue appears like a major
pain point relative to other remaining issues.
--
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
