Last modified: 2011-04-14 15:14:23 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 T17908, 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 15908 - Namespace dropdown on Special:Import is confusing
Namespace dropdown on Special:Import is confusing
Status: NEW
Product: MediaWiki
Classification: Unclassified
Export/Import (Other open bugs)
unspecified
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2008-10-09 04:34 UTC by Mike.lifeguard
Modified: 2011-04-14 15:14 UTC (History)
3 users (show)

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

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

Description Mike.lifeguard 2008-10-09 04:34:26 UTC 
The (all) option in that dropdown really means "Put it in whatever namespace it's coming from." Perhaps "same" would be better than "all."
Comment 1 Chad H. 2008-10-09 15:29:40 UTC 
The major problem with that option (besides the naming) is that said namespace _might_ not be defined on the importing wiki...I'd suggest only giving that option if the namespace exists.
Comment 2 Mike.lifeguard 2008-10-09 15:59:47 UTC 
(In reply to comment #1)
> The major problem with that option (besides the naming) is that said namespace
> _might_ not be defined on the importing wiki...I'd suggest only giving that
> option if the namespace exists.
> 

Exists or has an equivalent. When importing from another language, the namespaces will be named differently. This even occurs between projects - the project namespace changes from project to project within a single language.

I suppose that'd be related to bug 15387, and possibly bug 5770.
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