Re: [SMARTY-DEV] Re: [SMARTY] Smarty Install Problems
| From: | .SMK. | Date: | Tue, 16 Jul 2002 21:28:26 +0000 |
| Subject: | Re: [SMARTY-DEV] Re: [SMARTY] Smarty Install Problems | ||
| References: | 1 | Groups: | php.smarty.dev |
| Request: | Send a blank email to php-smarty-dev+get-198@lists.php.net to get a copy of this message | ||
Ah, no, _get_include_path() already does this check for you, and returns
true/false (this is what the code snippet should tell :)
-----Ursprüngliche Nachricht-----
Von: Monte Ohrt [mailto:monte@ispi.net]
Gesendet: Dienstag, 16. Juli 2002 23:20
An: .SMK.
Cc: smarty-dev@lists.php.net
Betreff: Re: [SMARTY-DEV] Re: [SMARTY] Smarty Install Problems
I thought about a message saying the directory doesn't exist, but then
you have to explicitly check for it. When the directory could be
anywhere in the include path, that is a lot of checks.
Maybe just a good error message if the file is not found? Or maybe an
error message at the time the file was trying to be written and failed.
.SMK. wrote:
>>Check your $template_dir setting, and make sure the web user can write
>>to that directory. '\N117\N11726....' looks like it should have
>>something in front of it, like 'c:\path\to\templates_c\N117\...'
>
>
> @Monte:
> Well, ok, maybe it was not a good idea to simply create the directory,
> but a nice error message would make life much easier. No?
>
> _get_auto_filename() in Smarty.class.php:
>
> // auto_base not found, try include_path
> if(!$this->_get_include_path($auto_base,$_include_path)) {
> trigger_error( ... );
> } else {
> $res = $_include_path . DIR_SEP;
> }
>
>
>
--
Monte Ohrt <monte@ispi.net>
Director of Technology, ispi Inc.