That's weird, because it hides it for me. I have a field like this: objects_path = models.CharField(maxlength=50, null=True, editable=False)
and it is clearly not visible in the admin. Tamara D. Snyder wrote: > It just makes the field not editable. Actually, it looks like you > can edit the field - type in new stuff, etc. - but when you hit save, > that field is not saved. This is fine with me, because what I > *really* wanted was to keep knuckleheads from changing the slug > field. I'd also like to hide it (to make it less tempting to the > knuckleheads), so I'll try the javascript thing. For some reason I > was concentrating on just the hiding part and didn't even think of > using "editable=false" until you mentioned it. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---