Last modified: 2014-10-26 17:17:20 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 T34606, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 32606 - duplicate link: is not HTML-linked to file page, not red and points to the wrong URL
duplicate link: is not HTML-linked to file page, not red and points to the wr...
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
UploadWizard (Other open bugs)
unspecified
All All
: Normal trivial (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-11-23 15:33 UTC by Saibo
Modified: 2014-10-26 17:17 UTC (History)
11 users (show)

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


Attachments

Description Saibo 2011-11-23 15:33:01 UTC
FF 3.6 on openSUSE 11.1

When I try to upload a file which was already uploaded before but was deleted UW displays a warning about this and includes a link to the file. However this link is 
<pre>
<a href="#">andere Datei</a>
</pre>
but should be
<pre>
<a href="//commons.wikimedia.org/w/index.php?title=File:Burning_eyes_smileygree2tra4.png&action=edit&redlink=1">andere Datei</a>
</pre>
Otherwise a middle click on it doesn't work. I did it since it seems to be a usual link to a file page on Commons. 

Please also color it red if it doesn't exist and use the &action=edit&redlink=1 URL params.
Comment 1 Mark Holmquist 2012-05-30 22:21:29 UTC
OK, so to be clear, the reason this is a problem is because the link opens a modal dialog with, potentially, a _list_ of files for the user to see. I don't think modifying the way this works is the answer. Can we somehow display a list of files to the user in a non-intrusive way that doesn't involve a link which might be misunderstood? Showing the list in the file's div is out of the question, it might be too long. Showing the modal dialog right away is far too intrusive. What would be the better option, here?
Comment 2 Mark Holmquist 2012-08-23 20:58:52 UTC
OK, so, since this is actually a feature (to support multiple files) and it hasn't gotten any attention despite my question 2.5 months back, I'm going with INVALID for now. Please reopen if it's really that big of a problem....I agree it could be annoying, but it's a minor, minor bug.

Thanks!
Comment 3 Saibo 2012-08-24 16:41:35 UTC
Fine, close all bugs as invalid. ;-) Interesting strategy to reduce the high number of bugs. It is quite offensive to close all the bugs as invalid. Why did I invest time to report them? Because I just want to write a bug report? Or because there is something wrong?!

Make it a button instead of a fake link to file - problem solved, hm?
Comment 4 Saibo 2012-08-24 16:42:45 UTC
Or make it like I proposed but use the onclick event to trigger the modal window. That way a middle/ctrl click should still work.
Comment 5 Mark Holmquist 2012-08-24 16:48:13 UTC
It was certainly not my intention to offend, and I think you know that. My goal here is, yes, to reduce the number of bugs in the queue--if someone came in and saw this bug, and spent time on it, it could be potentially detrimental.

If there's no other way to close the bug, I can try _exactly one thing_ to solve it, but if that doesn't work, I'm not going to make it a button, because that would be a severely ugly UI change....and when I notice that something is ugly, you have to know it's pretty bad (I am definitely not a designer of any kind).

Your work in reporting these issues is very much appreciated, but your accusation that I'm simply closing bugs willy-nilly is not. I think a lot before closing something.

In this case, I thought that a minor inconvenience (accidentally opening another tab) to a minor subset of people (people who use middle- or ctrl+click) was really not something we had to spend a lot of time on, but I'll give it a few minutes of consideration here.
Comment 6 Saibo 2012-08-24 16:52:17 UTC
I have unwatched all bugs now. Have fun.
Comment 7 Mark Holmquist 2012-08-24 18:17:15 UTC
OK, I guess we lost Saibo. In any case, after some digging (and sidetracking), I found that the problem is waaaay down in mediawiki/core/resources/mediawiki/mediawiki.jqueryMsg.js:605.

Basically, this shouldn't be href="#", it should be href="javascript:". It's a hack, but it's a helpful hack.

However, I can't test the effects of this, because there are still not proper reports of duplicate or duplicate-archive, which means I can't see these errors.

So, I guess we come back to "I'll revisit this."

Saibo, I'm adding you back. If you're adamant about not being informed about this bug's progress, feel free to re-remove, but I'm glad you're around to help focus people on bugs. I just wish sometimes you could be a little less accusatory about it :)
Comment 8 Derk-Jan Hartman 2012-08-29 23:01:33 UTC
https://gerrit.wikimedia.org/r/21975

The dialog now no longer ALSO triggers the link target. Ideally, when there is just 1 duplicate, we should just link to the file (with _blank) and not bother with the dialog.
Comment 9 db [inactive,noenotif] 2012-12-01 10:13:15 UTC
(In reply to comment #8)
> https://gerrit.wikimedia.org/r/21975

Status Merged, bug maybe resolved
Comment 10 Andre Klapper 2013-01-26 00:42:41 UTC
(In reply to comment #9)
> (In reply to comment #8)
> > https://gerrit.wikimedia.org/r/21975
> 
> Status Merged, bug maybe resolved

Saibo: Is this still an issue, or is this FIXED by this patch?
Comment 11 Nischay Nahata 2013-02-25 18:18:38 UTC
(In reply to comment #8)

>Ideally, when there
> is just 1 duplicate, we should just link to the file (with _blank) and not
> bother with the dialog.

I don't think this is a good solution as we it might seem confusing for the user if sometime its a link to a file and on other times it just opens up a dialog.

I think the bug is still reproducible, I will try to make a fix soon.
Comment 12 Nischay Nahata 2013-02-25 18:37:05 UTC
https://gerrit.wikimedia.org/r/50760
Comment 13 Nischay Nahata 2013-12-06 17:19:25 UTC
No longer working for WMF, so removing assignee to un-lick this cookie.

Only minor comments need to be addressed. This might be a good one for newbies.
Comment 14 Nemo 2013-12-26 10:48:35 UTC
(In reply to comment #13)
> Only minor comments need to be addressed. This might be a good one for
> newbies.

Good, let's add it as GCI task. :)
Comment 15 Quim Gil 2013-12-26 17:05:17 UTC
I'm happy to create a GCI task for this report. However, it is unclear to me what is the solution agreed that needs to be implemented.

We avoid sending GCI students to bug reports with discussions and unclear outcome. Do you mind adding a new comment summarizing the work that needs to be done? Thank you!
Comment 16 Nischay Nahata 2014-03-14 17:49:14 UTC
(In reply to Quim Gil from comment #15)
> We avoid sending GCI students to bug reports with discussions and unclear
> outcome. Do you mind adding a new comment summarizing the work that needs to
> be done? Thank you!

That's fair. In that case it should be just fixed by someone else.

Only a few design issues are left, the comments on the change explain them. I am sure Mark could advise on this on IRC.
Comment 17 Andre Klapper 2014-10-26 17:17:20 UTC
This needs input from design and/or mtraceur before adding the "easy" keyword here again, so it's clear for a new contributor what's the path to take and what is the expected solution here. Please elaborate.

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


Navigation
Links