(05-25-2016, 11:39 AM)spjonez Wrote: Narf Wrote:It's unexpected behavior and as such it has to be logged - that's all the reasoning there needs to be.
I understand what you're getting at but that response is not useful for debugging...
I didn't want to mix raw session commands with CI's so I overloaded the session library to add a method:
Code:
public function write_close( ) {
session_write_close( );
}
Well, I don't have another response.
If I did, we'd have the whole thing figured out by now.