Just swapped servers and noticed something I didn't know was definable. On the old one, when I echoed stuff from a long while loop for instance, whatever was being echoed was printed in the browser the moment it was available. Stop for a sec to calculate the next loop's stuff and print right away. Etc. It would slowly fill up the page until the whole script was executed. Now on my new server, the exact same script, when I click the 'go' button, doesn't load the next page until it's executed entirely (almost). Only when it's (nearly) done will it load the next page. It's sort of annoying because the incremental view was a nice 'progress bar' like feature. It echoes debug stuff amongst others so I'd rather know right away in the first loop when it's broken. Judging by this, I assume it's an Apache httpd.conf or php.ini setting. Is that correct and if so, what directive should I be looking for? Any documentation links you can give me to sus this out? Thanks.
Sounds like it could be the output_buffering php.ini setting ( maybe ). Have a look at http://www.php.net/manual/en/ref.outcontrol.php. If you still have access to your original server, you could try running a diff between the config files from the 2 machines and see if you can spot anything that way. John
is there anyway to do this inline. My asp aps I would flush the buffer as page loads. Anyone know the syntax for this in PHP? EDIT: in the previous listed link...
Can't compare files since old host was shared/virtual = no access. Though that would be great to do since I'm finding all sorts of little differences like my recent special character mess. I'll check out the buffering stuff. Thanks!