Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FR] Change existing redirect whose destination matches new redirect's legacy URL #46

Open
benface opened this issue Mar 8, 2019 · 2 comments
Labels
enhancement New feature or request

Comments

@benface
Copy link

benface commented Mar 8, 2019

Okay, sorry about the confusing title, but here are some "repro steps" to explain what I mean:

  1. Change the URI of an entry from entry-1 to cool-entry-1
  2. Notice it adds a redirect in Retour, cool
  3. Change the URI again from cool-entry-1 to awesome-entry-1
  4. Notice it adds another redirect in Retour, so now we have:
  • /entry-1 => /cool-entry-1
  • /cool-entry-1 => /awesome-entry-1

It would be great if Retour was smarter about it, and also changed the existing redirect, so we'd have:

  • /entry-1 => /awesome-entry-1
  • /cool-entry-1 => /awesome-entry-1

...and there would only be one redirection when going to /entry-1. Does that make sense?

Thanks a lot for the great plugin <3

@khalwat
Copy link
Contributor

khalwat commented Mar 14, 2019

Well, the problem is that at least currently, the redirects have no "memory" of whether they were automatically created or not, and what entry they are associated with or not.

For this to be feasible, it'd need to record information that a redirect was automatically created by Retour, and it'd need to know what element it is associated with.

@khalwat khalwat added the enhancement New feature or request label Mar 14, 2019
@benface
Copy link
Author

benface commented Mar 14, 2019

I see, that makes sense. Thank you for considering it :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants