Documentation error leads to 'model already registered exceptions'

[Marc]

The documentation says to add admin model registration to the end of the models.py file. Because this file may be imported more than once, this causes a 'model _ already registered exception'. The solution is to use autodiscover (as suggested in the documentation) but to place the model registration in the file admin.py.

See ​http://groups.google.com/group/django-users/browse_thread/thread/8af97d45102ee2f2 .

[Malcolm Tredinnick]

I cannot see where in admin.txt we are saying to put the registration in models.py. Please reopen the ticket if you are looking at an up-to-date checkout. Include the line number and file where you believe the problem is.

[wiremine@…]

I was able to reproduce the problem this way:

1. Part 2 of the tutorial suggests registering the model with the admin in the "Make the poll app modifiable in the admin" section.

2. If you then import a model as described in the "Generics" documentation, you then raise a "ImproperlyConfigured" exception.

The solution is to use admin.py instead of models.py

[James Bennett]

Duplicate of #7964.

[bb_cisze@…]

[]

[]

---

---

Replying to mtredinnick:

I cannot see where in admin.txt we are saying to put the registration in models.py. Please reopen the ticket if you are looking at an up-to-date checkout. Include the line number and file where you believe the problem is.

[Jacob]

Milestone 1.0 deleted