How to remove breadcrumbs in Django admin

[Marwan Al-Sabbagh]

For reference I've asked this question on stackoverflow:
http://stackoverflow.com/q/22345527/1699750

How can I use nav-global for navigation and hide the breadcrumbs in the
django admin app. I've found ways to do this but they seem hackish and
problematic. I'm looking for a clean reliable solution.

**Naive Approach that doesn't work:**

customize admin/base_site.html

{% extends "admin/base.html" %}
{% load i18n %}

{% block title %}{{ title }} | {% trans 'Django site admin' %}{%
endblock %}

{% block branding %}
{% trans 'Django administration' %}
{% endblock %}

{% block nav-global %}Some links will go here...{% endblock %}
{% block breadcrumbs %}{% endblock %}

this doesn't work because the templates in django admin like
change_list.html that extend base_site.html will define content for
breadcrumbs which will override whatever I have set in base_site.html.

**solution 1: CSS**

Add the following css to admin using the extrastyle block. This works, but
the breadcrumbs still get generated and appear in the HTML source. This
feels hacky.

.breadcrumbs {
display: none;
}

**Solution 2: override base.html**

Override base.html and remove the breadcrumbs block. Children will try to
define it but it never exists so it never gets rendered. This also seems
like a hack. It's also not a good idea to override base.html as each Django
release can make many changes to base.html and the admin app could break
between releases.

I just wanted to make sure there isn't some simpler way that I'm missing.
Thanks in advance.

Cheers,
Marwan AlSabbagh

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAPdSytJsGpcREnrfqK_B0hx_cW8byJaTc6wtL7OfgiGpvrVxog%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: "Beginning Geo Django: Rich Gis Web Applications With Python" Where can I get the book?

[ruomu sh]

Yes I understand. But I could not figure out how can I get it here at 
Nepal. I will buy it. I find different price listed on internet. Some site 
say it is out of stock. Is it published only limited copies?

On Friday, February 21, 2014 6:47:20 PM UTC+5:45, Tom Evans wrote:
>
> On Fri, Feb 21, 2014 at 10:15 AM, Ram Shrestha  
> wrote: 
> > Dear All, 
> > I am want to learn GeoDjango in real world application. I believe this 
> book 
> > "Beginning Geo Django: Rich Gis Web Applications With Python" is the 
> best 
> > book for me. But I could not download download it. 
> > 
> > If anyone have this book Please share the book with me. Where can I get 
> it 
> > for free! 
>
> If the author or publisher does not make this book available as a free 
> download, it is not appropriate to use this list to try to pirate it. 
>
> Doing so discourages future authors and publishers from writing books 
> about Django. 
>
>
> Cheers 
>
> Tom 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/4b73bce8-63fb-4eec-8725-b446bfbe7eb5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is there a good reason why Django querysets can't be intersected?

[James Bennett]

QuerySets have supported the '&' operator (as measured by implementing the
__and__() method) for as long as they've been in Django; the implementation
dates all the way back to 0.95.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAL13Cg-gDwDCW5oB1jeeaGrMBNGrCGST0TMiwDh2idC317THMQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is there a good reason why Django querysets can't be intersected?

[Shawn Milochik]

I don't know anything about efficiency, but it works at least as far back
as Django 1.3. I'd assume that, with lazy evaluation, it's probably about
as efficient as anything in the ORM.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAOzwKwHiR8HyHz-AaNoQbB6vQsFLun1jrn1W5XzVA7-qhsTm0A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is there a better way to do this?

[Gene Coetzee]

Very helpful, thanks Mike!

On Sunday, March 16, 2014 7:34:11 PM UTC-4, Mike Dewhirst wrote:
>
> On 17/03/2014 9:59am, Gene Coetzee wrote: 
> > Hi There! 
> > 
> > Starting out with Django, and was looking for a bit of guidance. I am 
> > trying to establish a Organizational structure for employee/supervisor 
> > type relationships. Since each of these individuals will be a user, I am 
> > extending trying to also take advantage of django's built-in 
> > contrib.auth package. 
> > 
> > In Short, employees report to supervisors, and in turn supervisors in 
> > themselves can report to their respective supervisors... I developed the 
> > following models, but was curious if there might be a better way to do 
> this: 
>
> There will be a few different opinions on this ... here's mine: 
>
> class Employee(models.Model): 
>  user = models.ForeignKey(User) 
>  def __unicode__(self): 
>  return self.user.username 
>
> class Relationship(models.Model): 
>  boss = models.ForeignKey(Employee) 
>  worker = models.ForeignKey(Employee) 
>  relationship_type = models.CharField(max_size=32) 
>  def __unicode__(self): 
>  return "{0} {1} {2}".format(boss, relationship_type, worker) 
>
> I just typed this without testing and I think you would need to read up 
> on 'related_name' and use null=True here and there to get it working. 
>
> I would choose this approach to get some flexibility with multiple 
> relationships between employees. Supervisors get supervised too. Also, I 
> might choose different field names than "boss" and "worker" if I was 
> doing this for myself. 
>
> Mike 
>
> > 
> > class Supervisor(models.Model): 
> > supervisor = models.OneToOneField(User) 
> > def __unicode__(self): 
> > return self.supervisor.username 
> > 
> > class Employee(models.Model): 
> > employee = models.OneToOneField(User) 
> > supervisor = models.ForeignKey(Supervisor) 
> > def __unicode__(self): 
> > return self.employee.username 
> > 
> > Thank you! 
> > 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> > Groups "Django users" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> > an email to django-users...@googlegroups.com  
> > . 
> > To post to this group, send email to 
> > django...@googlegroups.com 
> > . 
> > Visit this group at http://groups.google.com/group/django-users. 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/django-users/3c6cac23-7218-4c14-8039-2764217f6aad%40googlegroups.com
>  
> > <
> https://groups.google.com/d/msgid/django-users/3c6cac23-7218-4c14-8039-2764217f6aad%40googlegroups.com?utm_medium=email_source=footer>.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/911151f6-69f6-45e3-9f38-90251bb0e385%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is there a good reason why Django querysets can't be intersected?

[Ram Rachum]

Also, is it a recently added feature?


On Mon, Mar 17, 2014 at 2:33 AM, Ram Rachum  wrote:

> Oh my fucking God I'm an idiot. I distinctly remember it not working.
> Happy it's working!
>
> Is it implemented efficiently?
>
>
>
> On Mon, Mar 17, 2014 at 2:29 AM, Shawn Milochik wrote:
>
>> It seems to work for me:
>>
>> a = Client.objects.filter(name__istartswith='a')   b =
>> Client.objects.filter(name__iendswith='t')
>> print a.count()   print
>> b.count()
>>
>>
>> c = a & b print
>> c.count()
>>
>>  --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Django users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/django-users/SHT4Fka0uwQ/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> django-users+unsubscr...@googlegroups.com.
>> To post to this group, send email to django-users@googlegroups.com.
>> Visit this group at http://groups.google.com/group/django-users.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-users/CAOzwKwE8d%3DJNaP%3DLzsCwYQOvpkGOvumU0mCNv7sOZ0jKhyvw8Q%40mail.gmail.com
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CANXboVbURmS9Cvb2uZUpcXSMd9Hqkwuk9Dm7RvdTbfDrG3aBKA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is there a good reason why Django querysets can't be intersected?

[Ram Rachum]

Oh my fucking God I'm an idiot. I distinctly remember it not working. Happy
it's working!

Is it implemented efficiently?


On Mon, Mar 17, 2014 at 2:29 AM, Shawn Milochik wrote:

> It seems to work for me:
>
> a = Client.objects.filter(name__istartswith='a')   b =
> Client.objects.filter(name__iendswith='t')
> print a.count()   print
> b.count()
>
>
> c = a & b print
> c.count()
>
>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "Django users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/django-users/SHT4Fka0uwQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/CAOzwKwE8d%3DJNaP%3DLzsCwYQOvpkGOvumU0mCNv7sOZ0jKhyvw8Q%40mail.gmail.com
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CANXboVaiTjsHS3rpnYEbVS6_w7YQzH45n3aS2cmDOk8fGnyEpg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is there a good reason why Django querysets can't be intersected?

[Shawn Milochik]

It seems to work for me:

a = Client.objects.filter(name__istartswith='a')   b =
Client.objects.filter(name__iendswith='t')
print a.count()   print
b.count()


c = a & b print
c.count()

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAOzwKwE8d%3DJNaP%3DLzsCwYQOvpkGOvumU0mCNv7sOZ0jKhyvw8Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Is there a good reason why Django querysets can't be intersected?

[cool-RR]

Hi everyone,

I understand that there's no way to get the intersection of two querysets 
in Django. Whenever I need to get the intersection of two querysets, I need 
to refactor my code to get pure Qs for those querysets and intersect those. 
This can be annoying sometimes.

My question: Is there a good reason why Django querysets can't be 
intersected? Do you think it should be implemented?


Thanks,
Ram.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/b6b3a367-e5c0-4440-98b6-5a9d78a78db3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is there a better way to do this?

[Mike Dewhirst]

On 17/03/2014 9:59am, Gene Coetzee wrote:

Hi There!

Starting out with Django, and was looking for a bit of guidance. I am
trying to establish a Organizational structure for employee/supervisor
type relationships. Since each of these individuals will be a user, I am
extending trying to also take advantage of django's built-in
contrib.auth package.

In Short, employees report to supervisors, and in turn supervisors in
themselves can report to their respective supervisors... I developed the
following models, but was curious if there might be a better way to do this:


There will be a few different opinions on this ... here's mine:

class Employee(models.Model):
user = models.ForeignKey(User)
def __unicode__(self):
return self.user.username

class Relationship(models.Model):
boss = models.ForeignKey(Employee)
worker = models.ForeignKey(Employee)
relationship_type = models.CharField(max_size=32)
def __unicode__(self):
return "{0} {1} {2}".format(boss, relationship_type, worker)

I just typed this without testing and I think you would need to read up 
on 'related_name' and use null=True here and there to get it working.


I would choose this approach to get some flexibility with multiple 
relationships between employees. Supervisors get supervised too. Also, I 
might choose different field names than "boss" and "worker" if I was 
doing this for myself.


Mike



class Supervisor(models.Model):
supervisor = models.OneToOneField(User)
def __unicode__(self):
return self.supervisor.username

class Employee(models.Model):
employee = models.OneToOneField(User)
supervisor = models.ForeignKey(Supervisor)
def __unicode__(self):
return self.employee.username

Thank you!


--
You received this message because you are subscribed to the Google
Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to django-users+unsubscr...@googlegroups.com
.
To post to this group, send email to django-users@googlegroups.com
.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/3c6cac23-7218-4c14-8039-2764217f6aad%40googlegroups.com
.
For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups "Django 
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/532634F3.1080300%40dewhirst.com.au.
For more options, visit https://groups.google.com/d/optout.

Is there a better way to do this?

[Gene Coetzee]

Hi There!

Starting out with Django, and was looking for a bit of guidance. I am 
trying to establish a Organizational structure for employee/supervisor type 
relationships. Since each of these individuals will be a user, I am 
extending trying to also take advantage of django's built-in contrib.auth 
package. 

In Short, employees report to supervisors, and in turn supervisors in 
themselves can report to their respective supervisors... I developed the 
following models, but was curious if there might be a better way to do this:

class Supervisor(models.Model):
supervisor = models.OneToOneField(User)
 def __unicode__(self):
return self.supervisor.username

class Employee(models.Model):
employee = models.OneToOneField(User)
supervisor = models.ForeignKey(Supervisor)
 def __unicode__(self):
return self.employee.username

Thank you!


-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/3c6cac23-7218-4c14-8039-2764217f6aad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Extended profile not being saved django-allauth

[voger]

I am trying to extend the user profile according to this page
https://docs.djangoproject.com/en/1.6/topics/auth/customizing/#extending-the-existing-user-model

I am using django-allauth for registration. My problem is that when the 
user registers I can't find any new rows in the database. The table is 
empty. Moreover if I do like the documentation says


u = User.objects.get(username='test1')
>>> print u
test1
>> users_data = u.userprofile.gender
Traceback (most recent call last):
  File "", line 1, in 
AttributeError: 'User' object has no attribute 'userprofile'

Can someone please help me? I trying for a long time to solve this and 
Google confuses me even more.



My model.py is:

from django.contrib.auth.models import User
from django.db import models
from cities_light.models import Country


class UserProfile(models.Model):
# This line is required. Links UserProfile to a User model instance.
user = models.ForeignKey(User, unique=True)

#define a touple with available gender choices
GENDER_CHOICES = (
('m', 'Male'),
('f', 'Female'),
)


# gender can take only one of the GENDER_CHOICES options
gender = models.CharField(max_length=1, choices=GENDER_CHOICES, 
verbose_name='Gender')

birth_date = models.DateField(verbose_name='Birth Date')
country = models.ForeignKey(Country, verbose_name='Country', 
max_length=50, default="")
post_code = models.CharField(verbose_name="Postal Code", 
max_length=5, default="")
has_accepted_tos = models.BooleanField(default=False, 
verbose_name='I accept site roules')
is_18_or_older = models.BooleanField(default=False, verbose_name='I 
am at least 18 years old')
area_of_residence = models.CharField(verbose_name='Area', 
max_length=50, default='')


# Override the __unicode__() method to return something meaningful!
def __unicode__(self):
return self.user.username

User.profile = property(lambda u: 
UserProfile.objects.get_or_create(user=u)[0])



My forms.py is:

from datetime import date

from django.contrib.auth import get_user_model
from django.forms import CharField, BooleanField, Form, ChoiceField, 
DateField

from django.forms.extras import SelectDateWidget
from django.forms import ModelChoiceField
from django.utils.translation import ugettext as _
from cities_light.models import Country

import utils


yearNow = date.today().year

GENDER_CHOICES = (
('m', _('Male')),
('f', _('Female')),
)


class SignupForm(Form):
has_accepted_tos = BooleanField(
error_messages={'required': _('You must accept the terms and 
conditions')},

label=_('I accept site terms and conditions'),
required=True)
is_18_or_older = BooleanField(
error_messages={'required': _('You must be at least 18 years 
old to use this site')},

label=_('I am at least 18 years old'),
required=True)
gender = ChoiceField(GENDER_CHOICES, label=_('Gender'), required=True)
country = 
ModelChoiceField(queryset=Country.objects.all().order_by('name'), 
label=_('Country'),

   required=True, empty_label=None, initial=89)
post_code = CharField(max_length=5, min_length=5, label=_('Postal 
Code'), required=False)
birth_date = DateField(widget=SelectDateWidget(years=range(yearNow 
- 18, yearNow - 100, -1)), required=True,

   initial="", label=_('Birth Date'))
area_of_residence = CharField(required=False, max_length=50, 
label=_('Area'))


class Meta:
model = get_user_model()
# model = UserProfile

def save(self, user):
print user
user.has_accepted_tos = self.cleaned_data['has_accepted_tos']
user.is_18_or_older = self.cleaned_data['is_18_or_older']
user.gender = self.cleaned_data['gender']
user.country = self.cleaned_data['country']
user.post_code = self.cleaned_data['post_code']
user.birth_date = self.cleaned_data['birth_date']
user.area_of_residence = self.cleaned_data['area_of_residence']
user.save(force_update=True)


def clean(self):
cleaned_data = super(SignupForm, self).clean()
country = cleaned_data.get('country')
post_code = cleaned_data.get('post_code')
area = cleaned_data.get('area_of_residence')

error_msg = _(u"Location not found")

if utils.verify_signup_location(country=country.code2, 
area=area, post_code=post_code) is False:

self._errors["post_code"] = self.error_class([error_msg])
self._errors["area_of_residence"] = 
self.error_class([error_msg])


del cleaned_data["post_code"]
del cleaned_data["area_of_residence"]

return cleaned_data


and in my settings.py I have

AUTHENTICATION_BACKENDS = DEFAULT_SETTINGS.AUTHENTICATION_BACKENDS + (
"guardian.backends.ObjectPermissionBackend",
# Needed to login by username in Django admin, regardless of `allauth`

Re: problem with integrating bootstrap 3.1.1 and django 1.6

[Camilo Torres]

On Sunday, March 16, 2014 1:58:50 AM UTC-4:30, rafiee.nima wrote:
>
> I'm using development server . and when i use   href="{{STATIC_URL}}css/bootstrap.css" rel="stylesheet" media="screen"> it 
> seems work correctly but when I use  media="screen">  my project file and directory structure is like :
>
>1. root project folder
>1. app folder
>2. static
>   1. css
>  1. bootstarp.css
>  2. js
>   3. img
>   3. media 
>4. template
>   1. app 
>   1. base.html
>   
> Hello,

 

should be:



Camilo

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/f01e1098-fbfd-47dc-aca3-69ffbb1de06a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: problem with integrating bootstrap 3.1.1 and django 1.6

[rafiee.nima]

I'm using development server . and when i use   it 
seems work correctly but when I use   my project file and directory structure is like :

   1. root project folder
   1. app folder
   2. static
  1. css
 1. bootstarp.css
 2. js
  3. img
  3. media 
   4. template
  1. app 
  1. base.html
 


On Friday, March 14, 2014 7:49:32 PM UTC+3:30, Tom Evans wrote:
>
> On Fri, Mar 14, 2014 at 2:33 AM, Camilo Torres 
>  
> wrote: 
> > python manage.py startapp testapp 
> > 
> > Inside the newly created test app directory, create static/css/ and put 
> your 
> > file there. Now try to reload your template to see if the template 
> loads. 
> > 
> > This may make it work for you, but in your case, is not the final 
> solution. 
> > You may need to actually put these static files that are 'site global' 
> in a 
> > central location in your filesystem, let's say: 
> /var/www/static/(css|js|etc) 
> > 
> > To do that, you need to add a setting to your settings.py: 
> > 
> > STATICFILES_DIRS = ( 
> > '/var/www/static/', 
> > ) 
> > 
> > That way you put all of your static site wide files inside 
> subdirectories in 
> > a common path. 
>
> This advice is wrong, do not copy your static files from 
> /static to a folder listed in STATICFILES_DIRS. 
>
> STATICFILES_DIRS is a list of _additional_ project folders that are 
> searched for files _in addition_ to your application static files. 
>
> However, you do need to copy the files from your application static 
> directories _and_ your project static file directories to the 
> directory specified by STATIC_ROOT. You do not do this manually, the 
> management command collectstatic does this for you. You also only need 
> to do this in production, in development (using runserver), the static 
> files are served for you by runserver. 
>
> For complete info on static files, there is an excellent step-by-step doc: 
>
> https://docs.djangoproject.com/en/1.6/howto/static-files/ 
>
> Cheers 
>
> Tom 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/3b32d61d-3465-4c00-87a5-f11dfb33e702%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.