According to T43#15315, renaming a Phabricator project breaks links because Phabricator doesn't create redirects. Phabricator should probably support graceful renames (leaving behind a redirect and not breaking links), similar to how MediaWiki behaves.
Even adding alternative hashtags doesn't solve this issue, as, for example, https://phabricator.wikimedia.org/tag/MediaWiki-extensions-Flow/ does not redirect to https://phabricator.wikimedia.org/tag/flow/
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Qgil | T910 Renaming Phabricator project breaks links (doesn't create redirects) | |||
| Resolved | • chasemp | T86772 Next Phabricator upgrade on 2015-02-18 | |||
| Invalid | • chasemp | T89824 post T86772 |
The solution we are applying currently is to add the former project name as
additional hash tag manually when renaming a project. See
http://m.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Renaming_projects
Explicitly upstreamed as https://secure.phabricator.com/T7092 . Can we add the Wikimedia umbrella to this? There doesn't seem to be a workaround, and this breaks the rename workflow.
The https://phabricator.wikimedia.org/tag/MediaWiki-extensions-Flow/ vs https://phabricator.wikimedia.org/tag/flow/ is interesting. It does work in the case of say https://phabricator.wikimedia.org/tag/opsen/ vs https://phabricator.wikimedia.org/tag/operations/.
So there are two issues I think. One is "making a project name create an automatic alternative hashtag by default", and the other is "some alternative hashtags do not redirect as intended".
Just wanted to clarify that, both issues seem credible and @Qgil I would imagine will be ok with adding the #wikimedia tag to upstream T7092. Thanks @valhallasw
Yes, there are at least two separate issues here, hence my separate report. But looks like upstream wants to handle together anyway.
The PHID links like https://phabricator.wikimedia.org/maniphest/task/create/?projects=PHID-PROJ-sonaen6vy6yloezadwqc are permanent, aren't they?
This should be fixed now. Details: https://secure.phabricator.com/rPac504f232fedf236736e7633c53ce64270809248