Re: SESSION error -> Your script possibly relies on a session side-effect which existed until PHP 4.2.3.

From: "Rik Wasmus" <luiheidsgoeroe@xxxxxxxxxxx>
Date: Tue, 29 Apr 2008 15:09:44 +0200

On Tue, 29 Apr 2008 15:00:35 +0200, Erwin Moller <Since_humans_read_this_I_am_spammed_too_much@xxxxxxxxxxxxxxxx> wrote:

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?

Sure, lots of values aren't specifically set in many normal php.ini, so they just take the default (which sadly in this case would be "on" for both of them). Just set them & reload Apache.
--
Rik Wasmus
.

Follow-Ups:
- Re: SESSION error -> Your script possibly relies on a session side-effect which existed until PHP 4.2.3.
  - From: Erwin Moller

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
- Re: SESSION error -> Your script possibly relies on a session side-effect which existed until PHP 4.2.3.
  - From: Erwin Moller

Prev by Date: Re: I couldn't understand why PHP is so popular. The PHP code looks so horrible compared with Java.
Next by Date: Re: getting absolute directory path?
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):
- Date
- Thread

Relevant Pages

Re: SESSION error -> Your script possibly relies on a session side-effect which existed unti
... warnings. ... Nonsense indeed, amen. ... I include an ini_set routine in all my projects these days, ... Do you think I could just add them, kick Apache, and be done with it? ...
(comp.lang.php)
Garbage collection and previous variable value
... code, in the routine AA: ... use strict; ... use warnings; ... previous value of a lexical scoped variables? ...
(comp.lang.perl.moderated)
Re: ${DBI::errstr} vs $DBI::errstr
... >warnings. ... Is there an explanation for this? ... This is because there is a routine DBI::errstrand therefore it is ... Peter Scott ...
(perl.beginners)
Re: stack traces for warnings?
... and have created a script that uses the 2 modules. ... I'm already using this in my code; the warnings are comming ... The warnings are not capricious statements from the guts of Perl. ... if your routine requires values to be ...
(comp.lang.perl.misc)
rmdir
... That routine creates a subdirectory based on the file name and then writes ... use strict; ... use warnings; ... my $fext = ""; ...
(perl.beginners)