Redirect module support

Created on 8 April 2024, 12 months ago
Updated 6 May 2024, 11 months ago

Problem/Motivation

If you have a path that is a 404 but has a valid redirect, the redirect will never be trigger as part of this module.

Steps to reproduce

Add a redirect for a path that does not exist
Visit the path
Verify you get the 404 page, not the redirected page.

Proposed resolution

Check if a redirect exists and send the user there rather than to the 404 page.

Remaining tasks

Figure out tests

User interface changes

N/A

API changes

N/A

Data model changes

N/A

Feature request
Status

Postponed: needs info

Version

2.0

Component

Code

Created by

🇳🇿New Zealand danielveza Brisbane, AU

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @danielveza
  • Merge request !27[#3439338] - Add redirect support → (Open) created by danielveza
  • 🇳🇿New Zealand danielveza Brisbane, AU

    Got a basic MR up. Still need to think about how tests work when you need a require a module outside of the ecosystem.

  • Pipeline finished with Failed
    12 months ago
    Total: 143s
    #140512
  • First commit to issue fork.
  • Status changed to Postponed: needs info 11 months ago
  • 🇩🇪Germany Grevil

    The test failures were unrelated, but I can not reproduce this issue with current 2.x-dev (aka 2.2.0-beta1). Is it still a problem for you using the latest release?

Production build 0.71.5 2024