Sorry, I was referring to the state and zip fields. After modifying my model, doing a sqlreset, and implementing the changes, they now show up. Thanks!
I was confused between the functionality of the forms and the fields in models. I'll get into the widget usage in the forms when building more of the frontend I assume. Why is this functionality not implemented in admin as easily as it is in the forms usage? To me, this would be pretty useful in the admin area as well, just a thought. On Mar 30, 3:55 pm, Evert Rol <[EMAIL PROTECTED]> wrote: > > I have a model: > > > from django.db import models > > from django import newforms as forms > > from django.contrib.localflavor.us import forms as us_forms > > > class Address(models.Model): > > member = models.ForeignKey(Member, unique=True) > > street = models.CharField(max_length=50) > > city = models.CharField(max_length=30) > > state = us_forms.USStateSelect() > > zip = us_forms.USZipCodeField() > > description = models.CharField(max_length=50) > > is_preferred = models.BooleanField(default=False) > > > I can't get Address.city or Address.state to show up in admin forms. > > What am I missing here? > > The only reason I can think of right now, is that you added those > later, after you initially created your models and the database. > Since city is practically the same as street, there shouldn't > otherwise be any difference between the two telling the admin not to > show the first. Unless you have code elsewhere that may prevent this. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
