Custom URLs & auto-generated URLs can conflict #2

Closed
jfro opened this Issue Feb 15, 2010 · 6 comments

Projects

None yet

2 participants

@jfro
Owner
jfro commented Feb 15, 2010

I believe there's currently no check to make sure there's no conflicting URLs between auto and manual-custom URLs. Also custom URLs might not even check to see if another custom url was already used.

@alanhogan
Contributor

A possible solution is to, internally, make all URLs custom URLs; that is, auto-assign slugs instead of base36 translating to/from a numerical id. A migration could be made for existing auto URLs.

@jfro
Owner
jfro commented Feb 15, 2010

thanks for the info, definitely sounds like a reasonable method

@jfro
Owner
jfro commented Feb 17, 2010

it will now error out if you try to use a in-use custom url, still allows auto/custom conflicts

@alanhogan
Contributor

My dev branch has a migration that identifies conflicts and gives everything explicit slugs. Still need to rewrite automatic slug generation.

@alanhogan
Contributor

alanhogan/lessnmore@c2e750c completely resolves this issue, and a related one regarding custom URLs in the stats table.

@jfro
Owner
jfro commented Apr 2, 2010

merged alanhogan's fork, so this issue should be resolved

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment