Re: [PHPTAL] Cache / Compilation behavior

2008-05-08 Thread Brice Burgess
Kornel Lesinski wrote: On Thu, 08 May 2008 15:46:42 +0100, Brice Burgess <[EMAIL PROTECTED]> wrote: From the responses received thus far; it looks like PHPTAL does depend on a user-configured writable directory to compile its templates to? By default it uses PHP's sys_get_temp_dir() to get

Re: [PHPTAL] Cache / Compilation behavior

2008-05-08 Thread Kornel Lesinski
On Thu, 08 May 2008 15:46:42 +0100, Brice Burgess <[EMAIL PROTECTED]> wrote: My apologies for being vague. I meant 777 as the "lowest common denominator" because it's the "easiest". poMMo is open source software that is meant to be simple to install. The vast majority of users don't know wh

Re: [PHPTAL] Cache / Compilation behavior

2008-05-08 Thread Brice Burgess
Kornel Lesinski wrote: On Thu, 08 May 2008 02:43:45 +0100, Brice Burgess <[EMAIL PROTECTED]> wrote: Having users set proper permissions on a "working" directory crosses eyes... let alone the introduces the possibility of a security risk as "777" is the lowest common denominator here! 0700 i

Re: [PHPTAL] Cache / Compilation behavior

2008-05-08 Thread Kornel Lesinski
On Thu, 08 May 2008 10:43:27 +0100, Iván -DrSlump- Montes <[EMAIL PROTECTED]> wrote: What about using an .htaccess to deny access on the output directory? In the ideal case scenario it should be outside the document root of the web server (not accessible from the internet). Of course they s

Re: [PHPTAL] Cache / Compilation behavior

2008-05-08 Thread Iván -DrSlump- Montes
What about using an .htaccess to deny access on the output directory? In the ideal case scenario it should be outside the document root of the web server (not accessible from the internet). Iván On Thu, May 8, 2008 at 11:09 AM, Kornel Lesinski <[EMAIL PROTECTED]> wrote: > On Thu, 08 May 2008 02:

Re: [PHPTAL] Cache / Compilation behavior

2008-05-08 Thread Kornel Lesinski
On Thu, 08 May 2008 02:43:45 +0100, Brice Burgess <[EMAIL PROTECTED]> wrote: Having users set proper permissions on a "working" directory crosses eyes... let alone the introduces the possibility of a security risk as "777" is the lowest common denominator here! 0700 is the lowest, if you ma

Re: [PHPTAL] Cache / Compilation behavior

2008-05-08 Thread Krzysztof Sikorski
Yes, PHPTAL uses a temporary directory to store compiled versions of the templates. It uses system's tmp directory by default (via sys_get_temp_dir() function or intelligent guess) - and if that doesn't suit you, you can always configure it by a PHPTAL_PHP_CODE_DESTINATION constant or setPhpCodeDes

[PHPTAL] Cache / Compilation behavior

2008-05-07 Thread Brice Burgess
I am about to embark on the rather burdensome quest of refactoring a semi-large codebase (poMMo) to utilize PHPTAL as its template engine (vs. Smarty). One of the reasons I want to switch from SMARTY is to alleviate the requirement of a writable directory (smarty requires this for compiling t