Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:8908 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 23251 invoked by uid 1010); 3 Apr 2004 03:17:10 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 23212 invoked by uid 1007); 3 Apr 2004 03:17:10 -0000 Message-ID: <20040403031710.23210.qmail@pb1.pair.com> To: internals@lists.php.net References: <20040402235607.94267.qmail@pb1.pair.com> <002501c4191b$534c0980$de00000a@alphaweb.net> <20040403025308.77620.qmail@pb1.pair.com> Date: Sat, 3 Apr 2004 05:17:14 +0200 Lines: 38 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Posted-By: 81.0.87.200 Subject: Re: is_readable stricter than it should be (PHP5 only?) From: lunakid@neuropolis.org ("Luna Kid") 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" 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.