search

google-code-export / django-hotclub

Automatically exported from code.google.com/p/django-hotclub
MIT License
0 stars 0 forks source link

Slugs in blog posts - user shouldn't *have* to enter it. #81

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Currently, blog posts demand a slug.

The behavior should be that if he enters one, it'll be used. If he doesn't,
Django will automatically create one.

Original issue reported on code.google.com by anli...@gmail.com on 9 Oct 2008 at 1:23

GoogleCodeExporter commented 9 years ago 
We could and should use the AutoSlugField from django_extensions

Original comment by leidel on 18 Oct 2008 at 10:03

GoogleCodeExporter commented 9 years ago 
That would be this AutoSlugField:

http://code.google.com/p/django-command-extensions/source/browse/trunk/django_ex
tensions/db/fields/__init__.py

Original comment by olle.jonsson on 19 Nov 2008 at 1:08

GoogleCodeExporter commented 9 years ago 
Yep.

Original comment by leidel on 19 Nov 2008 at 4:08

GoogleCodeExporter commented 9 years ago 
+1

Original comment by jes...@gmail.com on 25 Nov 2008 at 8:54

GoogleCodeExporter commented 9 years ago 
This snippet could also do the trick:

http://www.djangosnippets.org/snippets/770/

Original comment by arocki...@gmail.com on 14 Jan 2009 at 6:55

GoogleCodeExporter commented 9 years ago

Original comment by pyDanny on 13 Mar 2009 at 3:43

GoogleCodeExporter commented 9 years ago

Original comment by leidel on 13 Mar 2009 at 9:06