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

RFC 34: Automatic redirects #34

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions text/034-redirects-admin-changes.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,10 +54,6 @@ If this is checked when the page is published with the new slug, a redirect to t

When unpublishing or deleting a page, the user can add a redirect from that page’s URL to another page. If they create one, they will be given the option to repoint existing redirects at the new page, delete the existing redirects, or (when not deleting) do nothing.

#### Deleting redirects when pages are created in their place
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it worth adding this to a "Not covered" section with reasons as to why not?
This way 1 year down the line we'd have a good reference.


Whenever a page is created, moved, or re-slugged in a way that causes it, or one of its descendants to clash with a redirect. That or those redirects should be deleted. The user should always be given a warning if this is going to happen, with an option of overriding it if they want to keep them.

### Redirect management

#### Searching for prefix redirects
Expand Down