On Mar 15, 10:44 am, Yuri Baburov <burc...@gmail.com> wrote: > Hello all, > > How do you like the following idea: > startproject command puts a fixture for django.contrib.sites (and > fixture for superuser probably) to the root folder or whatever, to be > loaded with syncdb? > That way also encourage users to get more familiar with fixtures. > Of course it's too far for 1.2, so it can be implemented with 1.3 timeline.
This I like. I also like the idea of sites prompting the user for a domain when syncdb creates the contrib.sites tables. Or maybe have the sites framework not add an 'example.com' entry on creation by default and let the system raise an exception when it tries to get the current site to remind the developer to add a site object. Or maybe instead of raising an exception, have it try to get SITE_URL from your settings. I once accidentally had for a few days my sitemaps all pointing to example.com because I forgot to change the url after a database purge. Ouch. Me honestly, I've never really liked the sites framework very much. I don't *hate* it, but it's always been something that got in my way more than it's granted me much convenience. The thing that bothers me is how the overwhelming majority of sites (I'm assuming) have no use for a sites framework, yet django kind of 'forces' you to use it for a lot of functionality. For instance, the syndication framework, sitemaps, the 'view on site' link in the admin interface, etc... -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
