Re: is_readable stricter than it should be (PHP5 only?)

From: Date: Sat, 03 Apr 2004 03:17:14 +0000
Subject: Re: is_readable stricter than it should be (PHP5 only?)
References: 1 2 3  Groups: php.internals 
Request: Send a blank email to internals+get-8908@lists.php.net to get a copy of this message
Cannot reproduce this any more. (It occured on two different Debian unstable installations, with PHP5-beta3 on apache 1.3.29(?) and the other with PHP5-RC1 on apache-ssl 1.3.29.0.2-4), with the same result: file could be read, still is_readable returned false). Now, let's hope I just missed something outside of PHP's scope. That happens to me quite easily... :-/ Good night, Sz. "Luna Kid" <lunakid@neuropolis.org> wrote in message news:20040403025308.77620.qmail@pb1.pair.com... > > > Tampering with a coWiki (www.cowiki.org) plugin, I noticed that > > > is_readable() returns false, when PHP actually *can* read the file. > > > (Just commented out an "if (!is_readable($sRealPath))" and then > > > all went fine, the plugin now can read the files...) > > > > > > Is there a known reason for or has anoyone bumped into this? (Just > > > asking so I can decide if I should put some efforts to investigating > > > this.) > > > stat() (of which is_readable() is a variant) was refactored slightly with > > PHP5. > > > > Take a look at the output of stat($sRealPath) and the user/group that the > > webserver is running as. It'll also help to know what OS/webserver/sapi is > > being used. > > > > -Sara > > OK, thanks for the hint, I'll try to find out more then to see if that's a problem > of PHP or something else. > > Cheers, > Sz.

« previous php.internals (#8908) next »