ID:               18917
 Updated by:       [EMAIL PROTECTED]
 Reported By:      [EMAIL PROTECTED]
-Status:           Feedback
+Status:           Closed
 Bug Type:         Output Control
 Operating System: RH 7.3
 PHP Version:      4.2.2
 New Comment:

Please try using this CVS snapshot:

  http://snaps.php.net/php4-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php4-win32-latest.zip




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

[2002-09-21 12:06:09] [EMAIL PROTECTED]

Reopen when you have tried the snapshot.



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

[2002-09-21 03:10:22] [EMAIL PROTECTED]

sorry, I am  out of my box  to ca  25 september 2002., so i can not 
cooperate :(

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

[2002-09-21 01:54:14] [EMAIL PROTECTED]

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.



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

[2002-08-20 23:12:48] [EMAIL PROTECTED]

Please try using this CVS snapshot:

  http://snaps.php.net/php4-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php4-win32-latest.zip



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

[2002-08-15 09:01:31] [EMAIL PROTECTED]

Error or Warnings in script, that use ob_start("callback") or
ob_get_contents() can cause buffer to be "cut off"  or completly
crippled and filled with trash ....

ob_start("callback_func")
{
// main loop
do something here  

output something here
}

function callback_func($buffer)
        {
$result=do_something( $buffer);
return $result;
}


if some error or waring occures in  main loop, content of the output
buffer may be 
crippled, seems that ob_get_content() returns some short snipplet of 
binary data  only , in my case it is   
U1tBuUe[^_]Wj  or shortened ( not all
length  of the output buffer  is parsed to callback_func).




I have sugestion, how PHP should treat errors in the output_buffered
scripts.
If error occures in the main loop (not in the callback function) ,all
output of the script with  error or waring messages appended  SHOULD be
passed as parameter to callback_function...

If error occures inside the callback_function, SHOULD BE at least error
message  send to browser.  

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


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

Reply via email to