| | 269 | Finally, note that you'll probably want to keep a normal (non-site-specific) |
|---|
| | 270 | ``Manager`` on your model, even if you use ``CurrentSiteManager``. As explained |
|---|
| | 271 | in the `manager documentation`_, if you define a manager manually, then Django |
|---|
| | 272 | won't create the automatic ``objects = models.Manager()`` manager for you. |
|---|
| | 273 | Also, note that certain parts of Django -- namely, the Django admin site and |
|---|
| | 274 | generic views -- use whichever manager is defined *first* in the model, so if |
|---|
| | 275 | you want your admin site to have access to all objects (not just site-specific |
|---|
| | 276 | ones), put ``objects = models.Manager()`` in your model, before you define |
|---|
| | 277 | ``CurrentSiteManager``. |
|---|
| | 278 | |
|---|