Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.#607028: Add README.txt to core has the background for this. We're running into issues where handbook pages are being moved around, with no redirect in place for old links. Having to patch core every time a URL changes isn't a good solution IMO. If we had the path_redirect module enabled, we could set it up so that documentation editors who can move pages around can update the redirects.
The other option mentioned by dww is to patch this feature into the drupalorg.module, but that means that we'd still need a patch to be deployed there to fix any broken URLs.
Comments
Comment #1
dwwTo avoid any confusion, I'm in favor of turning on path_redirect, not adding more junk to drupalorg.module. I just mentioned it among the many possible options to solve this problem when deviantintegral asked me in IRC...
path_redirect is maintained by Dave Reid (on the security team, very responsible maintainer) and there's already a 7.x-1.x-dev snapshot available. It's fairly small and it does exactly what we need. I use it on a lot of sites and never had a problem.
Comment #2
dave reidI'd totally be in favor of this on d.org. I'd like to be able to clean up the code a bit first to make it appropriate for large-scale deployment. We already have custom redirection on our drupal.org modules but you have to maintain it in code and can't be easily/quickly changed.
Comment #3
dave reidBasically once I get to an offical 6.x-1.0 release, I'd feel comfortable doing this.
Comment #4
dave reidI could use input on #646950: Add an option to store redirects as menu router items instead of using hook_init().
Comment #5
dave reidMerging this into #780322: deploy path_redirect on drupal.org.