Merge global redirect functions into Redirect module

Created on 8 September 2010, over 14 years ago
Updated 1 November 2023, about 1 year ago

The Drupal 6 Global Redirect module provides a lot of features like:

  • Checks the current URL for an alias and does a 301 redirect to it if it is not being used.
  • Checks the current URL for a trailing slash, removes it if present and repeats check 1 with the new request.
  • Checks if the current URL is the same as the site_frontpage and redirects to the frontpage if there is a match.
  • Checks if the Clean URLs feature is enabled and then checks the current URL is being accessed using the clean method rather than the 'unclean' method.
  • Checks access to the URL. If the user does not have access to the path, then no redirects are done. This helps avoid exposing private aliased node's.
  • Make sure the case of the URL being accessed is the same as the one set by the author/administrator. For example, if you set the alias "articles/cake-making" to node/123, then the user can access the alias with any combination of case.

This patch aims to add those features (and the ability to configure them) into the Redirect module.

📌 Task
Status

Postponed

Version

1.0

Component

Code

Created by

🇮🇩Indonesia sylv3st3r

Live updates comments and jobs are added and updated live.
  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

  • Needs issue summary update

    Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇺🇸United States jenlampton

    Patch in #284 is working for me. Marking as RTBC.

  • Assigned to Kristen Pol
  • 🇺🇸United States Kristen Pol Santa Cruz, CA, USA

    Assigning to myself as I'm triaging all RTBC issues.

  • 🇨🇭Switzerland berdir Switzerland

    Note that this is a D7 issue, I'm not maintaining only 8.x-1.x, that was the original agreement with Dave and i think we shouldn'r be making non-trivial changes to 7.x-1.x at this point.

  • Status changed to Postponed over 1 year ago
  • 🇺🇸United States Kristen Pol Santa Cruz, CA, USA

    Thanks @Berdir. Yeah, I'm assigning everything that's RTBC to me in order to triage and see what is still valid and what's not and hopefully move issues forward or close them out.

    I agree that this is a major issue and might be dicey to merge at this point. It's a shame though given everyone's hard work. Though, there is a patch people can use that was RTBC'ed so they can always use that.

    I'd love to give issue credit for everyone's hard work on this but let me think how to best do that while marking this one as "won't fix". Postponing for the moment.

  • 🇳🇴Norway steinmb

    Given the current activity on D7 modules it might be difficult to legitimise the use of developer/maintenance time doing so. The issue is marked with "needs tests" though the patch introduce a single test with two assertions. Not sure if the tag was not removed or that this is too little tests. That might tip the scale. We could create a new branch and move this to, 7.x-2.x as an experimental feature. Not sure we win anything by doing so?

Production build 0.71.5 2024