Last modified: 2011-12-07 22:55:10 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 T34785, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 32785 - Attempt to &action=edit a "page" in the Media: namespace
Attempt to &action=edit a "page" in the Media: namespace
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
File management (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
http://en.wikipedia.org/w/index.php?t...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-12-03 20:08 UTC by LikeLakers2
Modified: 2011-12-07 22:55 UTC (History)
3 users (show)

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


Attachments

Description LikeLakers2 2011-12-03 20:08:20 UTC
NOTE: The link included in the bug info is NOT the one and only URL. It is just a link to an example of the error.

Attempting to add &action=edit (or ?action=edit ) to the end of a url of a page in the Media: Namespace (such as trying the link above to edit Media:Logo.png ) will bring up a MediaWiki internal error page. (see the link above for an example)
Comment 1 Bawolff (Brian Wolff) 2011-12-04 00:21:48 UTC
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.
Comment 2 Mark A. Hershberger 2011-12-05 17:51:01 UTC
(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?
Comment 3 Mark A. Hershberger 2011-12-05 17:56:46 UTC
Aaron says r103450... testing.
Comment 4 Mark A. Hershberger 2011-12-05 18:21:57 UTC
Doesn't appear relevant
Comment 5 LikeLakers2 2011-12-05 19:51:46 UTC
remark as unprioritized for priority.
Comment 6 Bawolff (Brian Wolff) 2011-12-05 21:59:43 UTC
(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
Comment 7 Mark A. Hershberger 2011-12-06 15:42:57 UTC
(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!
Comment 8 Bawolff (Brian Wolff) 2011-12-06 20:52:37 UTC
(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)
Comment 9 Mark A. Hershberger 2011-12-06 22:49:08 UTC
(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.
Comment 10 LikeLakers2 2011-12-07 22:55:10 UTC
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.

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


Navigation
Links