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

Post title change updates URL slug #43

Open
chadwithuhc opened this issue Apr 10, 2014 · 5 comments
Open

Post title change updates URL slug #43

chadwithuhc opened this issue Apr 10, 2014 · 5 comments

Comments

@chadwithuhc
Copy link

I think it would be better if the URL slug did not update with the title of the post. If a user posts a trick, then later on changes the title, the anyone linked to that page will break.

I propose one of a few options:

  1. Disable updating or URL slug. Once it's created, it's set (This could be seen as a bad feature though)
  2. Use a unique ID of some kind instead (I think this was mentioned elsewhere...)
  3. Somehow keep track of the changes and have a redirect to the new URL (This could be overkill)

Thoughts?

@stidges
Copy link
Member

stidges commented Apr 28, 2014

I think the second option would be best. But I kind of like to keep the URLs readable. We should think of a way to combine the two. Maybe something like /tricks/<id>/<slug>, where the slug is just as a 'readable detail' and the tricks get retrieved by the given ID?

@chadwithuhc
Copy link
Author

I think that is doable. I've always wondered, what do people think is the best solution for situations where someone tries to visit the URL without the slug, like /tricks/<id>? Do they just redirect them to the full URL to prevent duplicate pages, or give em a 404?

@stidges
Copy link
Member

stidges commented Apr 28, 2014

Hmm that's tough, I'd rather prevent that extra request / redirect..

@chadwithuhc
Copy link
Author

I agree, but the only reason they would get there is a bad link or trying to break the URL anyway... so it's not a common occurrence.

@stidges
Copy link
Member

stidges commented Apr 28, 2014

You're right. I'll look into the options and see if I can implement a change :)

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

No branches or pull requests

2 participants