If you make a boneheaded move such as creating a ModelAdmin class for a model that you forgot to include in your admin.py's model import statement, you get an error. But it's not the error you might expect. What happens is you get the "model already registered exception", citing the first model registered using admin.site.register().
I spent awhile looking around my app trying to see if I had indeed registered the model in question more than once via imports, but couldn't find it. When I fixed my error in the import statement, everything was fine. So definitely user error. But the error message Django displayed didn't help guide me to the problem. Worthy of a ticket or no? Derek Willis [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
