Opened 17 years ago
Closed 16 years ago
#6865 closed (invalid)
Information to be added on "Site matching query does not exist." error when trying to log in a user
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Using the documentation found here: http://www.djangoproject.com/documentation/authentication/#how-to-log-a-user-in, one may run into the error: "Site matching query does not exist."
The solution is to add a site to your sites table from within the Admin interface. This should be added to the documentation to increase understanding.
Change History (3)
comment:1 by , 17 years ago
Has patch: | unset |
---|
comment:2 by , 16 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:3 by , 16 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
If
django.contrib.sites
is inINSTALLED_APPS
and you've runsyncdb
, you do have aSite
object in your DB. If you've gone and deleted it manually, well, lots of things will break. Probably the best route is a separate issue -- adding a slightly stronger wording to the tutorial to indicate that messing with the defaults when you aren't aware of their dependencies is a bad idea.