Thanks... I thought it should be somewhere on the server side. I see that it is preferred to give users an option to manipulate slugs manually via an admin interface, that's why it is kept on the client side. If I prefer to do it on the server side I wouldn't need prepopulate_from parameter. Instead, I would build my form, and generate the slug from the data I receive explicitly. A few words on how prepopulate_from works can be added to the documentation.
omat On Jan 29, 6:14 pm, "Jonathan Buchanan" <[EMAIL PROTECTED]> wrote: > On 1/29/07, omat * gezgin.com <[EMAIL PROTECTED]> wrote: > > > > > > > About a year ago, there had been a discussion on a similar topic: > >http://groups.google.com/group/django-users/browse_thread/thread/ > > 006108ff1b23c36c > > > But most of the important points were left unanswered. The topic is > > expired, so I am starting a new one. > > > I think it is very important to be able to override the way the slug > > fields are generated. Dropping a non-ascii character should be done > > only if the character could not be mapped to its ascii cousin (ie. é - > > > e), both for generating more readable slugs and for reducing the > > frequency duplicate slugs. > > > But, I couldn't find where and how the slug fields are generated in > > the Django code. > > > Thanks for any comments... > > omatYou're looking for django/contrib/admin/media/js/urlify.js > > For its invocation, check out the > django.contrib.admin.templatetags.admin_modify.auto_populated_field_script > template tag, as used in > django/contrib/admin/templates/admin/change_form.html > > Jonathan. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
