Thank you, this works pretty well. Actually, "editable=false" does not hide the field from the admin, but it will keep the field from being edited, and I can use the javascript trick to make it hidden, so all is well for me.
Thanks a lot, guys! On Jul 26, 2006, at 4:02 PM, Sean wrote: > > Maybe you would want the "editable=False" parameter in your model, > which > hides the field from the admin. Then simply populate the field in the > save method. > > Tamara D. Snyder wrote: >> Hi all, >> >> In my "Event" model I have a slug field that is automatically >> generated from another field. I would like to hide the slug field >> from admin users, but still allow it to be automatically generated. >> I know I can hide it by using the "fields" parameter in the admin >> class of my model. But if I do this then the slug field is not >> automatically generated when I create a new event. Is there a way to >> hide the slug field, but still have it be filled in when I create a >> new event? >> >> Thanks! >> >> Tamara >> >>> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
