#24488: Optional SITE_ID when migrating django.contrib.sites
-------------------------------+--------------------------------------
Reporter: dimiro1 | Owner: nobody
Type: Bug | Status: new
Component: contrib.sites | Version: 1.8beta2
Severity: Normal | Keywords: sites, SITE_ID, database
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
The documentation says:
"get_current_site() will now lookup the current site based on
request.get_host() if the SITE_ID setting is not defined."
[https://docs.djangoproject.com/en/dev/releases/1.8/#django-contrib-sites]
When I try to migrate the project without the SITE_ID parameter, then I
got this error:
{{{
AttributeError: 'Settings' object has no attribute 'SITE_ID'
}}}
I know about the ticket https://code.djangoproject.com/ticket/23945
I think a better approach is to use the SITE_ID for the migration only if
the SITE_ID is configured in settings file, otherwise it must be auto
incremented as it were before.
--
Ticket URL: <https://code.djangoproject.com/ticket/24488>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/050.4bb5b0378b7dd20cf7e7748ee09d7077%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
