Re: [Django] #22482: Sites documentation suggest using initial data fixtures which are deprecated in 1.7

[Django]

#22482: Sites documentation suggest using initial data fixtures which are
deprecated in 1.7
---+--
 Reporter:  scibi  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.7-beta-1
 Severity:  Normal |   Resolution:  fixed
 Keywords:  sites, migrations  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Tim Graham ):

 In [changeset:"8c7d2edd45cc1f1a9c5146e3be9716fbcfcbc826"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8c7d2edd45cc1f1a9c5146e3be9716fbcfcbc826"
 [1.7.x] Fixed #22482 -- Recommended using data migrations in contrib.sites
 docs.

 Thanks scibi for the report.

 Backport of bbf0a9545b from master
 }}}

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.a29f6055fcc0deffe27cdcf3b4928bb2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22482: Sites documentation suggest using initial data fixtures which are deprecated in 1.7

[Django]

#22482: Sites documentation suggest using initial data fixtures which are
deprecated in 1.7
---+--
 Reporter:  scibi  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.7-beta-1
 Severity:  Normal |   Resolution:  fixed
 Keywords:  sites, migrations  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Tim Graham ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"bbf0a9545bd098f09aeb0c2fb63497eb0ddf13ad"]:
 {{{
 #!CommitTicketReference repository=""
 revision="bbf0a9545bd098f09aeb0c2fb63497eb0ddf13ad"
 Fixed #22482 -- Recommended using data migrations in contrib.sites docs.

 Thanks scibi for the report.
 }}}

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.45c0fd4d22f85975df92a75d6522b94f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22482: Sites documentation suggest using initial data fixtures which are deprecated in 1.7

[Django]

#22482: Sites documentation suggest using initial data fixtures which are
deprecated in 1.7
---+--
 Reporter:  scibi  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.7-beta-1
 Severity:  Normal |   Resolution:
 Keywords:  sites, migrations  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by scibi):

 IMHO it should be possible to initialize `sites` automatically while
 deploying the project. So it would be great to have a way of doing this
 described in the docs.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.c9144790db7123b1d3b4e714ead4b7ea%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22482: Sites documentation suggest using initial data fixtures which are deprecated in 1.7

[Django]

#22482: Sites documentation suggest using initial data fixtures which are
deprecated in 1.7
---+--
 Reporter:  scibi  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.7-beta-1
 Severity:  Normal |   Resolution:
 Keywords:  sites, migrations  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by rtnpro):

 I believe that "initial data fixture" does not map directly to
 automatically loading of 'initial_data.' fixtures. You can load
 the fixtures with {{{ python manage.py loaddata  }}} as well
 as by a custom migration (which does not need any fixture AFAIK).

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.746f2043559c25a931b5a31ae981f595%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22482: Sites documentation suggest using initial data fixtures which are deprecated in 1.7

[Django]

#22482: Sites documentation suggest using initial data fixtures which are
deprecated in 1.7
---+--
 Reporter:  scibi  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.7-beta-1
 Severity:  Normal |   Resolution:
 Keywords:  sites, migrations  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timo):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Accepted
 * needs_tests:   => 0
 * needs_docs:   => 0


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.8a7f446d3cc51c014eea7f0af00d1c45%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22482: Sites documentation suggest using initial data fixtures which are deprecated in 1.7

[Django]

#22482: Sites documentation suggest using initial data fixtures which are
deprecated in 1.7
---+---
 Reporter:  scibi  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  1.7-beta-1
 Severity:  Normal |   Keywords:  sites, migrations
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+---
 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'`.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/048.c5ea87ad571dae669f0d670de881b076%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.