1.4.X STATICFILES_FINDERS

I was able to prove that certain combinations of STATICFILES_FINDERS will result in no html output (no stylesheets or javascript on the rendered page).

On 1.3.X I was using:

STATICFILES_FINDERS = [
    "pipeline.finders.FileSystemFinder",
    "pipeline.finders.AppDirectoriesFinder",
    "pipeline.finders.PipelineFinder",
    "pipeline.finders.CachedFileFinder",
]

After upgrading to 1.4.x and updating my templates to use the new tags pipeline, stylesheet, javascript I discovered the problem and found that using the following works:

STATICFILES_FINDERS = [
    "django.contrib.staticfiles.finders.FileSystemFinder",
    "django.contrib.staticfiles.finders.AppDirectoriesFinder",
    "pipeline.finders.PipelineFinder",
    "pipeline.finders.CachedFileFinder",
]

[emyller]

Following up: I’ve just read the finder.py sourcecode and found this:

class FileSystemFinder(PatternFilterMixin, DjangoFileSystemFinder):
    """
    Like FileSystemFinder, but doesn't return any additional ignored patterns
    This allows us to concentrate/compress our components without dragging
    the raw versions in too.
    """
    ignore_patterns = [
        '*.js',
        '*.css',
        '*.less',
        '*.scss',
        '*.styl',

If FileSystemFinder is supposed to ignore CSS, SCSS, JavaScript, etc files, how could it ever find the files to work with? Either it is very wrong or we’re all missing the point of how/when to use it.

[vskh]

Including pipeline.finders.AppDirectoriesFinder into STATICFILES_FINDERS breaks collectstatic for me as well. While source says that it excludes certain types of files on purpose to avoid copying them to STATIC_ROOT, I did not find any trace of logic in storage to resolve source files when compiling configured packages. As of version 1.6.11 I used for debugging it just follows the regular logic of static files storage, i.e. prepending requested files with STATIC_ROOT meaning that although it excludes files from collection it still looks for them in STATIC_ROOT 😦