id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 22482,Sites documentation suggest using initial data fixtures which are deprecated in 1.7,scibi,nobody,"Hi, Currently django.contrib.sites documentation suggest to use initial data fixtures to setup correct name and domain for the project (https://docs.djangoproject.com/en/dev/ref/contrib/sites/): `django.contrib.sites` registers a `post_migrate` signal handler which creates a default site named `example.com` with the domain `example.com`. This site will also be created after Django creates the test database. To set the correct name and domain for your project, you can use an initial data fixture. However automatic loading of fixtures has been deprecated in Django 1.7: https://docs.djangoproject.com/en/dev/howto/initial-data/#automatically-loading-initial-data-fixtures It would be nice if there was a description in the documentation how to setup sites configuration with migrations. I tried achieving this but without success - referring to `Site` model from `sites` in migration of some app leads to: `LookupError: No installed app with label 'sites'`. ",Bug,closed,Documentation,1.7-beta-1,Normal,fixed,"sites, migrations",,Accepted,0,0,0,0,0,0