If the slugs are something you're really concerned with... I would say
customize the change form to work the way you want.
Personally, I would rather the computer error on the side of not
breaking...instead of trying to anticipate what I want it to do this
time...vs next time vs a year from now.
Yeah that makes sense. I guess we just need to be more careful when
adding live posts. Maybe it wouldn't be a bad idea to add the
functionality on change if a post is anything but live. This way the
slug stays relevant to the title for drafts if the editor feels like
experimenting with different
Nick,
I can answer you first question...but not really the second...hopefully
someone else will come and explain that one to you...
re slugs: The prepopulated_fields are working as intended.
The reason being, say you've written a blog post. You've send that link out
to thousands and millions of
Hello,
I'm running django 1.2.3 on a local server and am still quite new to
django. I was working with the "practical django projects second
edition" book and implemented the prepopulated_fields option to auto
populate slugs from titles.
It works when I add a new post but it does not work when I
4 matches
Mail list logo
