On 8/14/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> 1. Created a new site
> 2. Removed example.com from the list of sites
> 3. Tried to use authentication and got the error "DoesNotExist at
> /accounts/login/"
> 4. Deleted and rebuilt the database, authentication works.
Did you actually delete the 'example.com' entry in sites? That will
probably break things, because by default your settings file will have
'SITE_ID = 1', and deleting that entry removes the object in the
database with an id of 1. The 'DoesNotExist' exception is a result of
that; Django's trying to look up a Site object with an id of 1, and
there isn't one anymore.
If instead you just edit the 'example.com' site to have your actual
domain and the name of your site, this problem shouldn't happen.
--
"May the forces of evil become confused on the way to your house."
-- George Carlin
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---