Re: #206298 spip: prerm script blindly removes directories
On Wed, Aug 20, 2003 at 07:53:41PM +0200, Gaetan Ryckeboer wrote:
>
> Not necessary. Web administrators may upload files via FTP, andspip
> users never use them onto spip ? If so, the files will stay in place
> in upload, instead of beeing integrated onto the spip tree at the
> right place, and being logged in the sql database.
In which case should you be deleting them? I would say no. While they
are in that directory, they are not used by spip and thus not really a
part of spip. The user(s) put them there, when in doubt, leave them
there.
> Yes it needs. I've still moves documentation to usr/share/doc, instead
> of spip/ecrire/doc, but it is rather different with the cache and
> other application managed files.
>
> You may access the php files via apache, but php files may access to
> other php file, or static file. For instance, to modify the
> configuration, or read the cache.
Yes, symlinks are needed for direct file access (unless you patch the
source). Sorry, when I stated symlinks weren't needed I meant on the
Apache side. I've dealt with this exact problem in my packaging of
Media Mate (new name for Movie Mate). I'm currently using symlinks to
allow the php script to access files by the paths they expect and Apache
Alias directives to allow http requests to get the files without
enabling symlink following.
> I accept. Please send me examples in private, if you found a way to
> move php files accessing each other (via "include") in another
> directory, without patching the application.
I'll forward Media Mate's packaging over to you.
--
Jamin W. Collins
Remember, root always has a loaded gun. Don't run around with it unless
you absolutely need it. -- Vineet Kumar
Reply to: