Last modified: 2014-09-19 18:39:09 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T70296, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 68296 - Show duplicate error message
Show duplicate error message
Status: NEW
Product: MobileFrontend
Classification: Unclassified
Uploads (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: 68376
  Show dependency treegraph
 
Reported: 2014-07-20 13:46 UTC by Florian
Modified: 2014-09-19 18:39 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Florian 2014-07-20 13:46:46 UTC
If you try to upload an image (e.g. via Special:Uploads) which is an duplicate of another, the user becomes an success message and the image is added to Special:Uploads. A click to this only reloads the page and the image isn't uploaded (the same filename as the duplicate was set). I suggest to don't show an success toast and don't add the image to Special:Uploads (without a link to the duplicate one), better is to redirect to the location of the duplicate one. Maybe with an alert before, that the image is an duplicate and the user will be redirected to the duplicate.
Comment 1 Bingle 2014-07-20 13:50:21 UTC
Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/bPHX1l53
Comment 2 Jon 2014-09-19 18:39:09 UTC
I did this purposely. I thought it was more gratifying to feel like your image had been accepted then try to explain it already exists but I guess it is confusing as refreshing the page shows it is no longer there.

I guess errors are the way to go but low priority now this is not enabled on Wikimedia.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links