AutoSlugField changes slugs that end in numbers consufing them with autoincrementing "next" value

[jjdelc]

I have an entry titled "Articles 2010", and generate the "articles-2010" slug for it. When I update the entry, AusoSlugField will think that the "2010" part of the slug was the incremental "next" value, and when it finds that there were no 2009 entries with slug "article" before it, it will update the slug to "article", thus breaking a slug that shouldn't have changed.

[jjdelc]

Here's a patch that I'm using.
http://gist.github.com/464710

[gtaylor]

This is also burning us, would much like to see it addressed.

The patch is no longer valid due to upstream changes, but this is still an issue on Aug 24, 2011.

[sdornan]

This bug makes the AutoSlugField unusable for me.

[sdornan]

This is what I ended up doing:
sdornan/django-extensions@3e0a018

It's definitely a hack, but seems to work okay for my purposes. You would probably run into trouble if you wanted to modify the uniqueness constraints on the AutoSlug field after the fact.

[martino]

guys this is serious, bug still there at Sep 11, 2012. This should definitely be fixed, AutoSlugField is unusable otherwise...

[trbs]

I still don't see a pull request with tests, docs and a clear description of the solution.

[martino]

here we go

[nostalgiaz]

+1

[camilonova]

@trbs seems this issue can be closed.