Last modified: 2014-11-20 15:18:24 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 T41642, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 39642 - blank title throws error: "mw.Title: Could not parse title ".jpg""
blank title throws error: "mw.Title: Could not parse title ".jpg""
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
UploadWizard (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2012-08-25 08:44 UTC by Derk-Jan Hartman
Modified: 2014-11-20 15:18 UTC (History)
3 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Derk-Jan Hartman 2012-08-25 08:44:17 UTC 
I blanked the field of the title in preparation to pick another name, and I got:

 mw.Title: Could not parse title ".jpg"
Comment 1 Derk-Jan Hartman 2012-08-25 16:45:25 UTC 
The destination filename check relies on a mw.Title object.

you can not have "File:.jpg"  as a valid title object, so errors are thrown. Worse, you cannot fallback to returning null, because this is the only location keeping track of the file extension.

Point of note. is it wise to have this as a mw.Title ? you can't seem to enter 'invalid titles' this way, which might be a bad UI experience ?
Comment 2 Nischay Nahata 2013-02-15 20:30:18 UTC 
https://gerrit.wikimedia.org/r/#/c/49280/
Comment 3 Andre Klapper 2014-09-09 18:52:44 UTC 
Patch has a -1 plus needs rebase.

Nischay: This issue has been assigned to you a while ago. 
Could you inform us whether you are still working (or still plan to work) on this issue? 
Only in case you do not plan to work on this issue anymore, should the assignee be set back to default and the bug status changed from ASSIGNED to NEW/UNCONFIRMED? Thanks.
Comment 4 Andre Klapper 2014-11-20 15:18:24 UTC 
Nischay Nahata: I am resetting the assignee of this issue to default because there has been no signs of progress for the last months. Feel free to assign it to yourself again when you plan to work on this. Thanks for your understanding.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links