That's a valid consideration, but yes, if I enabled that field to be populated based on another field, I would expect it to change regardless of it was a add form or a change form. The attribute doesn't read "sometimes_prepopulate_fields". Nor does it read "always_prepopulate_fields" for that matter. But the lack of clarity seems to suggest always...
keith On Wed, Oct 1, 2008 at 11:01 AM, Carl Meyer <[EMAIL PROTECTED]> wrote: > > On Sep 30, 9:27 pm, "Keith Eberle" <[EMAIL PROTECTED]> wrote: > > Yea... I didn't know for sure, but I thought it used to. That's why I > > asked. I wonder why that functionality wasn't there by default... > > Because in many cases it would be a usability problem. What if you've > manually adjusted the slug - do you really want your manual changes > automatically erased anytime you touch the prepopulate_from field? > > If you really want a fully-automatic, non-editable slug field, > consider doing it on the server side with one of the many snippets on > djangosnippets.org. > > Carl > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
