ID:               14529
 Updated by:       [EMAIL PROTECTED]
 Reported By:      [EMAIL PROTECTED]
 Status:           Critical
 Bug Type:         Output Control
 Operating System: Linux RH 7.2
 PHP Version:      4.3.0-dev
 New Comment:

Well it looks like I isolated the problem... and it's not PHP related.

The FTP package I've been using has been truncating files that it has
been sending to our server for some reason.  I only just discovered
this today as it did it to a non-PHP document that I sent (one of only
a few).

I've changed to another FTP package and sent the PHP docs I was having
trouble with to our server (RH 7.2/Apache 1.3.20/PHP 4.0.6) and they
ran OK. I'm not sure whether it was an FTP client or server problem
(client more likely, but maybe clients are having problems dumping php
files onto a specific FTP server build?)

The FTPD we're running is WU FTPD 2.6.1 - others with this problem
might want to check this isn't happening to their too.


Previous Comments:
------------------------------------------------------------------------

[2002-03-17 20:30:02] [EMAIL PROTECTED]

Is it just me or does the output bug show up more often after a
session_destory and then a header("location to another page?

When I successfully use my login page it redirects me to a startpage
which NEVER shows up wrong. When I logout from this page via a logout
link it destoys the session and the redirects me to the login page. The
login page NEVER EVER shoes up correctly upon using this "route". If I
reload it it shows up nicely.

/Fabbe

------------------------------------------------------------------------

[2002-03-17 20:15:36] [EMAIL PROTECTED]

Sorry...
About the loginpage in my previous comment: I explained wrong and I
think I have an interesting point to notice.
The loginpage sometime crashes in one of two ways:
 It stops loading at the same spot,
 and when posting data to login the script doesn't ignores the
header(location call) as if the session i just registered isn't there.

My point is that it seems like the session doensn't register correctly
even if it does so half the time and it always did with 4.0.x. Nuf
said...

------------------------------------------------------------------------

[2002-03-17 20:09:47] [EMAIL PROTECTED]

I'm experiencing the same problem. Pages sometimes get cut off, always
in the same place. I'm having the problem on some of my pages and not
all of them. The most annoying occrunce is on a login-page which loads
correctly way to seldom and makes it almost impossible to login. The
bug wasn't there in 4.0.x but when we upgraded to 4.1.x it is... We
haven't been able to go back to 4.0.x to ensure that it isn't apache
that messes up but we don't think so.
Example of bug:
www.svenskamagic.com
(the last part of the page shows up corrupted sometimes)
www.svenskamagic.com/club_login.php
(page stops at the same spot all the time and it's hard to login when
posting data with the form. An interesting point is that when the page
works and you make a faulty login it shows an error-output "Wrong
user/pass", but when the page doesn't work upon logging in, it doesn't.
It's like it just reloads the page without any form data sent to it.(if
the form data would be there it would leave the error mess))
www.svenskamagic.com/phpinfo.php
(info about the server)

------------------------------------------------------------------------

[2002-03-17 11:50:01] [EMAIL PROTECTED]

Sorry, don't mind my previous post. I had a bug in my template system.

------------------------------------------------------------------------

[2002-03-17 11:19:53] [EMAIL PROTECTED]

I found an interesting detail. On my windows box running PHP 4.1.1 and
Apache 1.3.23, it only stops on "=" signs.
I had a template that has some "=" signs in it, and by replacing the
first accurence, it goes on until the next one.
I'm using output buffering, but it outputs the content anyway. The
interesting fact is that it only turncates the output while echoing the
buffer.

------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/14529

-- 
Edit this bug report at http://bugs.php.net/?id=14529&edit=1

Reply via email to