|
|
Posted by Jerry Stuckle on 01/30/08 13:36
white lightning wrote:
> On Jan 30, 1:19 pm, Jerry Stuckle <jstuck...@attglobal.net> wrote:
>
>> OK, what do you have in $_SESSION when it fails?
>>
>> echo "<pre>\n";
>> print_r($_SESSION);
>> echo "</pre>\n";
>>
>
> when it fails, i get an empty array: Array(). Obviously, it has logged
> out and has removed all the session values.
>
Not so obvious to me. All it shows is that you have an empty session
array. There could be plenty of reasons - bad session id, for instance.
Or the server not storing the session information properly, or any of
about 100 other reasons.
So, in your login code, set another variable in the session which you
don't clear. is the $_SESSION array still empty?
>> Do you have full error reporting and display_errors enabled on the
>> failing server?
>>
>
> on the failing server, display_errors is on and error_reporting is set
> to 2039
>
Which means E_NOTICE is disabled. You should have it enabled, also.
Any messages then?
>> What are thePHPversions on the two systems?
>>
>
> localhost: PHP Version 5.2.1
> Failing server: PHP Version 4.4.7
>
>
That should be OK - except that PHP 4.x is now past end of lifetime.
Your hosting company should have upgraded to 5.x months ago. That part
bothers me. If they haven't upgraded their PHP, is there something else
they're not doing correctly?
Maybe that's an unfounded worry, but I don't know. Two types of admins
bother me - those who upgrade immediately after something comes out, to
maintain "the latest and greatest", and those who don't upgrade until
they have to replace the hardware.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
Navigation:
[Reply to this message]
|