Re: A patch to keep cache directory out of webroot

jojodee wrote:
   <snip>
> Where i'm also going with this, is trying to work out a generalized storage 
> mechanism for Xaraya files and you may be interested in this in that 
> specifically atm, I'm was trying to work out where we can put image files as 
> part of all this.
> Category (data) images was a point in question. I'd like them out of the 
> Xaraya core file directory tree - and that poses a few problems. However, 
> whatever the answer for that i think it needs to be a solution that can be 
> applied systematically in other areas of specific 'module required' 
> writeable, web accessible and non-webaccessible space, outside the core 
> directory tree, and either in our out of the webdoc root :). Also where we 
> can maintain template overrides and have either (multi)site wide, or theme 
> specific images - for example :)
> <snip>
> Jo

Well, something I thought of, when the thread started, was to have 
perhaps a 'system' folder for xaraya specific files and a seperate 
folder for site specific files.  One thing I have an issue with (and 
it's strictly with myself, not with xaraya) is when I edit a function 
within a module, I often forget to back it up before deleting and 
upgrading :)

So, what I was thinking is have a system folder, named whatever, with a 
directory structure capable of handling whatever xaraya core and modules 
needed to operate properly (as the var directory does now).  Then have a 
non-system folder for images used on the site, module function overides 
(even additional functions?), things such as that with a similar but 
simpler structure.  Basically, the non-system folder would be intended 
to plug into the system, instead of replacing any of it.

Template overides, well, that is part of this I haven't worked out yet. 
  Themes.  Currently you can configure what directory themes are to be 
stored in the themes module.  What this allows is to use the same theme 
with different (multi)sites and each site have it's own templates to 
modify.  So, theoretically we can do that now as far as the template 
overrides being (multi)site wide or not.

The category images (i haven't read your other post) I think I can see 
where you are coming from, because an image has to have the same name to 
override one currently in the categories module from a theme, that is 
where a non-system folder would come in handy.  If each (multi)site has 
it's own non-system folder, modules that use images, such as the 
categories module, could simply check that folder for images instead of 
within the module itself.    I think the reason the categories module 
keeps it's own images and then allows you to override them is probably 
for a fall back in case that image isn't in a particular theme or 
something, so it may not be good to only check themes for category images.

I know, I'm just adding to the mix now aren't I :)  Just some thoughts. 
I'll always be around to bug you guys/ladies no matter what you decide 
to do.
~David.D