Skip to content
This repository


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Fixed #20634 - Corrected doc mistake re: staticfiles finders strategy.

Thanks claudep for the catch and bmispelon for the research.

Backport of 9be93aa from master.
  • Loading branch information...
commit 519fdacf5127540638f7c1b4a3656d9a31f16a8b 1 parent 9b0604e
Tim Graham authored June 21, 2013
2  docs/howto/static-files/index.txt
@@ -68,7 +68,7 @@ details on how ``staticfiles`` finds your files.
68 68
     Now we *might* be able to get away with putting our static files directly
69 69
     in ``my_app/static/`` (rather than creating another ``my_app``
70 70
     subdirectory), but it would actually be a bad idea. Django will use the
-    last static file it finds whose name matches, and if you had a static file
+    first static file it finds whose name matches, and if you had a static file
72 72
     with the same name in a *different* application, Django would be unable to
73 73
     distinguish between them. We need to be able to point Django at the right
74 74
     one, and the easiest way to ensure this is by *namespacing* them. That is,
4  docs/ref/contrib/staticfiles.txt
@@ -106,7 +106,9 @@ various locations.
106 106
 The default will find files stored in the :setting:`STATICFILES_DIRS` setting
107 107
 (using ``django.contrib.staticfiles.finders.FileSystemFinder``) and in a
108 108
 ``static`` subdirectory of each app (using
+``django.contrib.staticfiles.finders.AppDirectoriesFinder``). If multiple
+files with the same name are present, the first file that is found will be
110 112
111 113
 One finder is disabled by default:
112 114
 ``django.contrib.staticfiles.finders.DefaultStorageFinder``. If added to

0 notes on commit 519fdac

Please sign in to comment.
Something went wrong with that request. Please try again.