Chris Long wrote: > For the permission checking, See: > http://code.djangoproject.com/wiki/ExtendingAdminTemplates for more
Thanks, that's a neat trick, though from the surface I'm not 100% sure it will do what I'm thinking. I'll have to investigate further. My intuition tells me I need to do the checks in the model, maybe with a save hook, not in the template; but I may be off on that. > As for the second part, there are two possible routes... > 1) Override the default change/add manipulator for the model... > 2) Create a new field in the model that replaces the integer field you > are currently using... I am currently trying option 2, which is not as difficult as I thought it might be, thought I have gotten stuck. I've created a new field that subclasses models.Field, and a new form that subclasses forms.formField, both seem correct (at lest the models doesn't throw any errors when starting the server), however when I try manage.py syncdb appname, the manager errors: KeyError: "MyBitField" Does any one know where you include that code does the db creation stuff? Thanks again Chris. -- mthorley --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
