Last modified: 2008-12-29 20:20:34 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 T18834, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 16834 - Enable image moving on Wikimedia
Enable image moving on Wikimedia
Status: RESOLVED DUPLICATE of bug 15842
Product: Wikimedia
Classification: Unclassified
Site requests (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: shell
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-12-29 19:48 UTC by Victor Vasiliev
Modified: 2008-12-29 20:20 UTC (History)
1 user (show)

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


Attachments

Description Victor Vasiliev 2008-12-29 19:48:17 UTC
Please enable image moving on all Wikimedia projects since it's pretty stable now.

I've done some testing:
* Moving a simple image with 1 entry in the history -- works
* Referring to it from a old title -- works
* Moving image with a large histry -- works
* Protection from moving images to an incompatible extension -- works
* Protection from moving images to an invalid filename -- works
* Moving over another file -- didn't work, fixed, should work in trunk
* Merging two images with large histories -- got one awful bug when one version of image was multiplied 8 times in the history. Can't reporduce it. Works in all other cases, but it's possible to create a case when the latest version of the image is earlier than the previous, because only old versions are sorted.
* Splitting histories -- works

If you have any other test cases, tell me their results or just suggest them here.
Comment 1 MZMcBride 2008-12-29 20:20:34 UTC

*** This bug has been marked as a duplicate of bug 15842 ***

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


Navigation
Links