You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Slugs can now be changed easily via Sanity Studio. This risks killing shared links using older versions of the page slug.
Proposed solution: Make slug readonly after initial publish
Proposed solution:
Every time a slug is changed for a page, a redirection rule should be created to redirect the old to the new slug value.
Potential issues: - Page A changes from /dog to /cat, then page B changes from /cat to /dog. Automatic redirection would redirect /dog to /cat, making page B inaccesible. Or page B would take presedence and the old url for page A would be broken. So a possible solution would be for active slug values to take presedence, while redirection is a fallback. Ideally a warning should be presented when there are conflicts.
The text was updated successfully, but these errors were encountered:
Slugs can now be changed easily via Sanity Studio. This risks killing shared links using older versions of the page slug.
Proposed solution: Make slug readonly after initial publish
Proposed solution:Every time a slug is changed for a page, a redirection rule should be created to redirect the old to the new slug value.
Potential issues:- PageA
changes from/dog
to/cat
, then pageB
changes from/cat
to/dog
. Automatic redirection would redirect/dog
to/cat
, making pageB
inaccesible. Or pageB
would take presedence and the old url for pageA
would be broken. So a possible solution would be for active slug values to take presedence, while redirection is a fallback. Ideally a warning should be presented when there are conflicts.The text was updated successfully, but these errors were encountered: