This is already fixed on trunk...

I wonder if the fix for special:whatlinkshere/media:foo that's currently tagged 1.18wmf1 will fix this.

(In reply to comment #1)

I wonder if the fix for special:whatlinkshere/media:foo that's currently tagged
1.18wmf1 will fix this.

Just verified that this is in 1.18 tarball, too. What is the revision number you are talking about?

Aaron says r103450... testing.

Doesn't appear relevant

likelakers2 wrote:

remark as unprioritized for priority.

(In reply to comment #4)

Doesn't appear relevant

Yep, looks like I was wrong. On further investigation it appears to be fixed by r101656

(In reply to comment #5)

remark as unprioritized for priority.

Why? Please don't do that, especially without a better reason why.

(In reply to comment #6)

On further investigation it appears to be fixed by r101656

Thanks!

(In reply to comment #7)

(In reply to comment #5)

remark as unprioritized for priority.

Why? Please don't do that, especially without a better reason why.

To be fair, highest priority was probably a bit much. This bug would affect almost nobody. (You'd have to manually construct such a url)

(In reply to comment #8)

To be fair, highest priority was probably a bit much.

No argument there, but returning it to "unprioritized" is wrong, too.

likelakers2 wrote:

Well, there isn't much priority at this point. Actually, since apparently its been fixed on trunk, it really doesn't have a priority.

Marking as RESOLVED FIXED, per the above. Reopen this if needed.