Thanks for those pointers :D I'm also going to override prepare() to throw an
exception if the template needs parsing because this won't be allowed on a live
One thing I have noticed, however, is that 4 functions in the PHPTAL class are
private rather than protected:
Is there a specific reason for this or is it just historical? Obviously it is
much harder to subclass a class with private methods.
On 15 Aug 2012, at 14:08, Kornel Lesiński <kor...@geekhood.net> wrote:
> The hash is computed in PHPTAL::getFunctionName(). Filename is built from
> that name.
> Subclass PHPTAL class and override this method to compute unique name from
> path/settings you care about.
> Also override cleanUpGarbage() to stop it from deleting compiled templates.
> regards, Kornel
> On 15 sie 2012, at 09:59, Robert Goldsmith <rgoldsm...@names.co.uk> wrote:
>> Hi all,
>> We're implementing a deployment system using phars and pre-compiled
>> templates from phptal and things are mostly going well but we've noticed
>> that the template file hashes appear to be based on the full path of the
>> template when it is initially compiled. Obviously if we then move the
>> templates (put them in a phar and drop them on a different server) this
>> isn't going to work.
>> Has anyone attempted to change the way the template name hashes are
>> calculated before and can they give me some pointers as to the way to go
>> about doing it?
>> Robert Goldsmith
>> PHPTAL mailing list
> PHPTAL mailing list
PHPTAL mailing list