Last modified: 2009-10-28 19:12:59 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 T17219, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 15219 - Disable renaming of wiki sets to already existing names
Disable renaming of wiki sets to already existing names
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
CentralAuth (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Andrew Garrett
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-08-17 21:15 UTC by Filip Maljkovic [Dungodung]
Modified: 2009-10-28 19:12 UTC (History)
0 users

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


Attachments

Description Filip Maljkovic [Dungodung] 2008-08-17 21:15:00 UTC
Say you have a wiki set called A and a wiki set called B. http://meta.wikimedia.org/wiki/Special:EditWikiSets lists them both and http://meta.wikimedia.org/wiki/Special:EditWikiSets/1 and http://meta.wikimedia.org/wiki/Special:EditWikiSets/2 are places to edit the sets, respectively. However, if I move the set B to the name A, the software would show a success message and http://meta.wikimedia.org/wiki/Special:EditWikiSets will subsequently list only the set B. Set A still exists, though, and can be accessed by directly typing .../1 in the URL field. However, I don't think it's intuitive to be able to move over another set name and shadow it without any warning. So, there should be an error if you try to rename set B to A (since A already exists).
Comment 1 Filip Maljkovic [Dungodung] 2008-08-17 21:34:38 UTC
Oh, and another thing. Renaming the second set back to B doesn't automatically make A visible again (it does though after A's been renamed to something else, or likely after any change has been made to it).
Comment 2 Andrew Garrett 2008-08-20 22:58:51 UTC
Should be fixed in r39741.

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


Navigation
Links