On Mon, Jan 19, 2009 at 12:04 PM, Thiago F. Crepaldi <togn...@gmail.com>wrote:
> > hello Karen, > > below is the code required. I hope you can help me =) > In the future, please post code of that length/width to someplace like dpaste.com; email makes it quite hard to read given how it gets wrapped. I think what is happening is you have added a field to your model form that has a name that matches a related object accessor for the model (that is, you have added a field with a name that matches that of a model that has a ForeignKey that points to your Feature model). I've recreated the error with a much simpler model form based on the tutorial's Poll model: http://code.djangoproject.com/ticket/10069 I thought the fix was easy but a quick run of Django's model_forms test shows that the quick fix I was thinking of breaks something else, and I'm running out of time to look at this today, so it may be a little while before a fix goes in. In the meantime if you can identify the additional field(s) that may be causing the problem in your form, renaming them to something that doesn't exactly match the related model name(s) should work as a temporary workaround. Karen --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
