Closed (duplicate)
Project:
Drupal core
Version:
6.x-dev
Component:
file system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
18 Mar 2007 at 12:20 UTC
Updated:
30 Jan 2008 at 16:39 UTC
Drupal 5.x has a well-known problem that on cannot use the CSS aggregator, color picker, etc. with the file download method set to private. The obvious(?) solution to this would seem to be create a separate files directory for system files like these that is always public.
Comments
Comment #1
owen barton commentedLet's do it :)
Comment #2
ChrisKennedy commentedThere is a summer of code project to rework public/private file handling in Drupal - perhaps this can be an early milestone. The introduction post is at http://groups.drupal.org/node/3647
Comment #3
douggreen commentedI've done something similar to this on a 4.6.x. I made a few changes to file.inc to implement a new file_public_directory_path variable and function, and then used this where needed. Changes are also needed to system.module to add the setting to the settings form.
I've previously considered additional options that are maybe best left as a second step. I'm suggesting we not address possibilities such as giving some control to which files go in which directory, by file extension, by module, by user, etc.
The current settings are file_directory_path and file_downloads.
The smallest change I can think of is to add a new file_downloads option named FILE_DOWNLOADS_BOTH and a new setting file_public_directory_path, leaving file_directory_path to always be the private directory if either FILE_DOWNLOADS_BOTH or FILE_DOWNLOADS_PRIVATE are set. I'm not sure that the names here are best (FILE_DOWNLOADS_BOTH, file_public_directory_path). Are there other simple implementations?
Comment #4
catchhttp://drupal.org/node/166759
Comment #5
headkit commentedsubscribing