If person copies and pastes the full page name on to the move field, and doesn't realize there is a drop down box for namespace, the result is a repeated namespace.
We should warn if someone tries to move to Foo:Foo:Bar.
Version: 1.23.0
Severity: enhancement
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Add warning when repeated namespace in title | mediawiki/core | master | +46 -0 |
Hi,
I am working on this task. What would be a good alert message for the users when there is repeated namespace in title?
Any message that allows users to understand what exactly is the problem and how to fix the problem. :)
Also see https://lists.wikimedia.org/pipermail/wikitech-l/2017-February/087638.html for feedback.
Please suggest a good way to prompt a dialog box.
I tried OOjs UI/Windows/Message Dialogs but it gives a TypeError: OO.ui.MessageDialog is not a constructor.
Sounds like a general question about invoking dialogs. See https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker#Feedback.2C_questions_and_support for best places. :)
Change 339384 had a related patch set uploaded (by Shanikae):
Add warning when repeated namespace in title
This could be fairly annoying if the site intentionally uses page titles like this – the only one I'm aware of is German Wikipedia, with tons of pages like these:
('Kategorie' stands for 'Category', 'Vorlage' stands for 'Template'; no, I don't know why they do such a thing)
I'm not sure what the right solution is. It might be okay if we just use a less intrusive warning, like I suggested in the Gerrit changeset comments.
The proper solution is to get rid of the drop-down menu at Special:MovePage/Foo; cf. T50239: Special:MovePage's namespace dropdown menu needs further thought.
We could still catch "Category:Category:Foo" (same namespace) with a warning, perhaps. If someone wants to use "Wikipedia:Category:Foo" (different namespaces) when using a single input field (i.e., with no drop-down menu), we do not need to prevent or discourage that, in my opinion.
Untagging an old "good first task tag from 2014. This component of MW has no owner currently, which means it maybe difficult to find someone to make feature decisions, or a mentor, or get code review etc.
Removing task assignee due to inactivity, as this open task has been assigned to the same person for more than two years (see the emails sent to the task assignee on Oct27 and Nov23). Please assign this task to yourself again if you still realistically [plan to] work on this task - it would be welcome.
(See https://www.mediawiki.org/wiki/Bug_management/Assignee_cleanup for tips how to best manage your individual work in Phabricator.)