|
|
Posted by Name on 10/12/21 11:25
Alvaro G Vicario <alvaro_QUITAR_REMOVE@telecomputer.com> wrote in
news:1rfaitvx72bum.of3ms8pe67yz.dlg@40tude.net:
> *** Name wrote/escribiσ (Tue, 30 Aug 2005 21:24:14 GMT):
>> I have a site that has been working perfectly for a few years now,
>> under PHP 4.2.3. Since later versions of PHP run so much more
>> quickly, I wanted to update this site to one of those later versions.
>> Being a very cautious person, I started with 4.3.11, since it was
>> the highest version of the next PHP increment. When I tried this
>> version, my session file kept getting rebuilt (with the same name) as
>> though the session file found was old. The same thing has happened
>> to me all the way to version 5.0.4.
>
> A test you can do: backup php.ini and replace it with the old one from
> 4.2.3. If that way it works, compare settings and see what's
> different.
>
>
>
orry, I've tried the easy stuff (and some pretty tough stuff too). This
may be needed additional information. If I recreate PHP with all the same
configuration options, except to make it an Apache module, it works fine.
I would keep it this way, however, our security setup won't allow it on the
production system.
Now I'm no PHP expert. Was there a big (or subtle) change in how sessions
were handled between 4.2.x and future versions? I noticed there are
additional INI entries, but they seem to deal with 4.2.x compatibility and
security.
Thanks,
Vincent
Navigation:
[Reply to this message]
|