On Sat, May 05, 2001 at 07:04:50PM +0300, Zeev Suraski wrote:
That fixed the problem. Thanks!
> Can you check now? (update TSRM)
>
> At 18:46 5/5/2001, Jon Parise wrote:
> >On Sat, May 05, 2001 at 06:26:58PM +0300, Andi Gutmans wrote:
> >
> > > Can you please try and check on what date (and m
Can you check now? (update TSRM)
At 18:46 5/5/2001, Jon Parise wrote:
>On Sat, May 05, 2001 at 06:26:58PM +0300, Andi Gutmans wrote:
>
> > Can you please try and check on what date (and maybe what patch) broke
> this?
>
>I'm pretty sure it happened after May 2nd, but I don't have an
>exact time
On Sat, May 05, 2001 at 06:26:58PM +0300, Andi Gutmans wrote:
> Can you please try and check on what date (and maybe what patch) broke this?
I'm pretty sure it happened after May 2nd, but I don't have an
exact time. I quick scan of the cvs commit archives didn't turn
up anything obvious, but I
Can you please try and check on what date (and maybe what patch) broke this?
Thanks,
Andi
At 05:11 PM 5/5/2001 +0200, Jani Taskinen wrote:
>http://www.php.net/bugs.php?edit=1&id=10644
>
>And it happens to me too..
>
>--Jani
>
>
>On Sat, 5 May 2001, Andi Gutmans wrote:
>
> >By the way, can you
http://www.php.net/bugs.php?edit=1&id=10644
And it happens to me too..
--Jani
On Sat, 5 May 2001, Andi Gutmans wrote:
>By the way, can you open a bug report about this? Please include PHP
>version, Web server setup and short reproducing script.
>At the same time if one of you guys can get an
It probably depends on the setup.
Andi
At 05:35 PM 5/5/2001 +0300, Zeev Suraski wrote:
>I'm unable to reproduce it with the current CVS, btw.
>
>Zeev
>
>At 17:32 5/5/2001, Andi Gutmans wrote:
>>By the way, can you open a bug report about this? Please include PHP
>>version, Web server setup and
I'm unable to reproduce it with the current CVS, btw.
Zeev
At 17:32 5/5/2001, Andi Gutmans wrote:
>By the way, can you open a bug report about this? Please include PHP
>version, Web server setup and short reproducing script.
>At the same time if one of you guys can get an idea what broke this (
By the way, can you open a bug report about this? Please include PHP
version, Web server setup and short reproducing script.
At the same time if one of you guys can get an idea what broke this (or on
what day) that would be great. You can do a binary search by checking out
the PHP CVS by date.
At 06:58 PM 5/4/2001 -0400, Jon Parise wrote:
>On Fri, May 04, 2001 at 06:31:37PM -0400, Jon Parise wrote:
>
> > > >works fine here. Or do you meant something
> > > > else, Chuck?
> > >
> > > The value is set; it's just missing all path delimiters. So if the
> file is
> > > actually /var/www/
On Fri, May 04, 2001 at 06:31:37PM -0400, Jon Parise wrote:
> > >works fine here. Or do you meant something
> > > else, Chuck?
> >
> > The value is set; it's just missing all path delimiters. So if the file is
> > actually /var/www/foo/bar.php, echo __FILE__ gives me "varwwwfooobar.php".
> >
On Fri, May 04, 2001 at 04:28:56PM -0400, Chuck Hagenbuch wrote:
> >works fine here. Or do you meant something
> > else, Chuck?
>
> The value is set; it's just missing all path delimiters. So if the file is
> actually /var/www/foo/bar.php, echo __FILE__ gives me "varwwwfooobar.php".
> Which
Quoting Sebastian Bergmann <[EMAIL PROTECTED]>:
>works fine here. Or do you meant something
> else, Chuck?
The value is set; it's just missing all path delimiters. So if the file is
actually /var/www/foo/bar.php, echo __FILE__ gives me "varwwwfooobar.php".
Which means that dirname(__FILE__)
Chuck Hagenbuch wrote:
> It was a change in Zend (I'm nearly positive) that broke the __FILE__
> constant. I've heard one person verify this and one person say it
> works for them; can people running latest cvs (and latest cvs of
> Zend, as well) say if it works for them or not?
works fine
13 matches
Mail list logo
