Page MenuHomePhabricator

Flow: support Topic:OldPagename as a #REDIRECT
Open, LowPublicFeature

Description

When we enable Flow on a wiki and existing pages conflict with its Topic: namespace (or its localized aliases), we move those pages with the /namespaceDupes.php script. It would be nice to make Topic:OldPagename redirect. For example, https://en.wikipedia.org/wiki/Topic:_The_Washington_%26_Jefferson_College_Review

ErikB commented "if you have a revision in Topic: namespace that is wikitext (as opposed to flow-board) than that as a redirect is fine and will work"

The trick is to create a wikitext page in the NS_TOPIC namespace after Flow is enabled (which is what we need to do make the enwiki page above redirect). You can't do this by editing Topic:OldPagename , since the edit action is invalid for a Flow topic. As a workaround it seems you can Move an existing article into the Topic: namespace without changing its content model, and it continues to act like a redirect.

One glitch is if you view the Topic:OldPagename with ?redirect=no, Flow dies with "Model/UUID.php: Unknown input to UUID class" from Flow\Content\Content::onFetchContentObject(Article, WikitextContent). If Flow thinks it should occupy the page it ignores the class of the page's content.


Version: master
Severity: enhancement

Details

Reference
bz68846

Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 3:35 AM
bzimport set Reference to bz68846.
bzimport added a subscriber: Unknown Object (MLST).

(In reply to spage from comment #0)

it seems you can Move an
existing article into the Topic: namespace without changing its content
model, and it continues to act like a redirect.

That probably won't work on WMF wikis so long as $wgContentHandlerUseDB is false, see bug 49193.

Seems like an enhancement. Key phrase "It would be nice" :)

Aklapper changed the subtype of this task from "Task" to "Feature Request".Feb 4 2022, 11:13 AM
Aklapper removed subscribers: Spage, wikibugs-l-list.