Re: SESSION error -> Your script possibly relies on a session side-effect which existed until PHP 4.2.3.
- From: Erwin Moller <Since_humans_read_this_I_am_spammed_too_much@xxxxxxxxxxxxxxxx>
- Date: Tue, 29 Apr 2008 15:00:35 +0200
Rik Wasmus schreef:
<snip>
I'll immediately change the php.ini to surpress these nonsense warnings.
Nonsense indeed, amen.
Hi Rik,
I include an ini_set routine in all my projects these days, and added them over there. Now the warning is gone. :-)
And now for the fun part:
session.bug_compat_42 or session.bug_compat_warn both don't exists in my php.ini. sigh.
Am I expected to just add them?
I am used to changing ini values, but never added new ones before.
(and this is a productionserver)
Do you think I could just add them, kick Apache, and be done with it?
Regards,
Erwin Moller
.
- Follow-Ups:
- References:
- SESSION error -> Your script possibly relies on a session side-effect which existed until PHP 4.2.3.
- From: Erwin Moller
- Re: SESSION error -> Your script possibly relies on a session side-effect which existed until PHP 4.2.3.
- From: Erwin Moller
- Re: SESSION error -> Your script possibly relies on a session side-effect which existed until PHP 4.2.3.
- From: Rik Wasmus
- Re: SESSION error -> Your script possibly relies on a session side-effect which existed until PHP 4.2.3.
- From: Erwin Moller
- Re: SESSION error -> Your script possibly relies on a session side-effect which existed until PHP 4.2.3.
- From: Rik Wasmus
- SESSION error -> Your script possibly relies on a session side-effect which existed until PHP 4.2.3.
- Prev by Date: Re: Seeing encrypted code in php
- Next by Date: Re: I couldn't understand why PHP is so popular. The PHP code looks so horrible compared with Java.
- Previous by thread: Re: SESSION error -> Your script possibly relies on a session side-effect which existed until PHP 4.2.3.
- Next by thread: Re: SESSION error -> Your script possibly relies on a session side-effect which existed until PHP 4.2.3.
- Index(es):
Relevant Pages
|
