open_basedir and is_readable

open_basedir exhibits very annoying (and imho buggy) behavior in
generating warnings even when is_readable() is called, rather than
just returning false as appropriate. This means it is impossible to
use is_readable as a precondition before opening a file.

Is there any way to check the preconditions of reading a file without
generating warnings for files outside open_basedir?

On Feb 6, 2:26*pm, Arancaytar <arancaytar.ilya...@gmail.com> wrote:
> open_basedir exhibits very annoying (and imho buggy) behavior in
> generating warnings even when is_readable() is called, rather than
> just returning false as appropriate. This means it is impossible to
> use is_readable as a precondition before opening a file.
>
> Is there any way to check the preconditions of reading a file without
> generating warnings for files outside open_basedir?

Addendum: http://bugs.php.net/bug.php?id=37476 describes this behavior.

Arancaytar pisze:
> On Feb 6, 2:26 pm, Arancaytar <arancaytar.ilya...@gmail.com> wrote:
>> open_basedir exhibits very annoying (and imho buggy) behavior in
>> generating warnings even when is_readable() is called, rather than
>> just returning false as appropriate. This means it is impossible to
>> use is_readable as a precondition before opening a file.
>>
>> Is there any way to check the preconditions of reading a file without
>> generating warnings for files outside open_basedir?
>
> Addendum: http://bugs.php.net/bug.php?id=37476 describes this behavior.

I'm posting this just in case anyone looked for a quick solution: use
@is_readable.

--
CKFinder :: ajax web file browser
http://www.ckfinder.com