The server is outside my control. I have to plead with the admin to get any changes made. I have no access to previous settings, so can't tell you whether they are the same or not. My assumption is that whatever the default was on installation is what the settings in php.ini were set to both times.
Anyway, I got to thinking, maybe the sessions is expiring too quickly. If I add this code, will that tell me if I'm on the right track?
/* set the cache limiter to 'private' */
session_cache_limiter('private');
$cache_limiter = session_cache_limiter();
/* set the cache expire to 30 minutes */
session_cache_expire(30);
$cache_expire = session_cache_expire();
/* start the session */
session_start();
Adding the:
global $_SESSION;
global $_POST;
global $_GET;
was to get rid of a WARNING for session side-effects, see post Session Side-effect revisited. Until I added that code, I got that warning every time, even though I always coded as if register_globals was set to off even when they were set to on (before the server admin upgraded). I was told early on in my php learning process that using the register_globals feature was bad programming practice, so I never got into the habit of it. I always refer to the passed variables as $_SESSION['item1'], $POST['item2'], or $GET['item3'] instead of $item1, $item2, $item3 which is how you could do it if register_globals were turned on.
