> As I understand it in EmbperlObject.pm, line 206ff $searchpath is
> extended by paths from $ENV{EMBPERL_OBJECT_ADDPATH} _only_ when
> $basename is _not_ found earlier, while processing the directory
> hierarchie from dirname($req -> {inputfile}) down to
> $stopdir and the likes.
> I verified this behaviour by creating a <mydocroot>/temp/base.epo
> which tries to Execute header.epo, * and footer.epo and
> a corresponding <mydocroot>/temp/index.epo which I tryed to
> request. As I expected header.epo and footer.epo could not be
> found despite they exist in <mydocroot>/
>
> If this behaviour is intended I would be happy to know why...
>
This behaveiour was intended, but from my experience with using
EmbperlObject, it seems better to me to change it in the following way:
- If EMBPERL_OBJECT_STOPDIR is set, this directory is taken as the last
directory in the normal search path, instead of the directory where the base
template (base.epo in your case) is found.
- EMBPERL_OBJECT_ADDPATH is _always_ added to the search path
What do you think? Any other ideas?
Gerald
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
