Jump to content

Recommended Posts

Hey, i keep seeing people say that using output buffering is a lazy man's fix, so i started experimenting with ways to modify my framework to NOT use it. The funny thing is that i took out the ob_start (or whatever it is), and i'm not getting any errors when logging in, redirecting, etc. Is this because i have a cache in my php.ini?

 

output_buffering = 4096

 

Again, that is just in my php.ini, and there is NO ob_start in ANY of this new framework (i just copied the old, and am modifying it, but i already took out the buffering).

 

Nope, that's not it. I changed it to 0 and i'm still not getting any errors. I'm waiting for the "You already started sending output, you can't send a header now" kind of message. Yes, i remembered to restart apache after modifying php.ini.

 

Thanks.

Do you even know what output buffering is?

 

Make sure error reporting is on at the beginning of your scripts and check again.

ini_set('display_errors',1);
error_reporting(E_ALL|E_STRICT);

 

You are most likely not sending a problematic header after content if you turn caching off and check this.

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.