Last modified: 2011-04-14 15:14:28 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 14446 - Image with missing versions behave oddly
Image with missing versions behave oddly
Status: NEW
Product: MediaWiki
Classification: Unclassified
File management (Other open bugs)
All All
: Low normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2008-06-06 18:23 UTC by Siebrand Mazeland
Modified: 2011-04-14 15:14 UTC (History)
2 users (show)

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


Description Siebrand Mazeland 2008-06-06 18:23:53 UTC
From IRC: * See:
* Check version of 05:50, 4 June 2007
* The delete link is:
* when clicked and confirmed, all version are deleted.
* There are more files suffering from this:

Brion replied:
* that means one of the old file versions is missing
* it should recognize them in a sensible way
Comment 1 bdk 2008-09-17 18:30:15 UTC
Two more affected files as examples (the first version in each case):š_Castle_3.jpg

The "Date/Time" link to the file (in the "File history" section) only shows up as e.g. 
The filename at the end is missing.

Missing versions are always annoying, but the wrong delete link is more important. Yesterday I accidentally deleted two files because of these bogus links (luckily noticed it on the spot). Well, the delete link should lead to an error message in case a version does not exist.

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