Hi Djulia,
I think that might be an unrelated problem, but we'll need to check it out to know for sure.
What was happening with the previous error is that the AutoBackup plugin was calling backupDatabase() which had an optimization to "close" sessions before long backup operations. So all the patch does was "not" close sessions that were previously opened by CMSB.
If you want to print out what CMSB thinks the session name is you can add a debug line in /lib/init.php
// Initialize session
$session_name = cookiePrefix() . 'PHPSESSID'; // use a unique session cookie for each CMS installation
ini_set('session.name', $session_name); // sets session.name
die("ini_set('session.name', $session_name)");
And check the cookie prefix value which comes from /data/settings.*.php and is stored in 'cookiePrefix'.
You could also check what the session name and ID is before that line:
print "session_name(): " .session_name(). "<br/>\n";
print "session_id(): " .session_id(). "<br/>\n";
if (!isset($_SESSION)) { session_start(); }
Actually, I'm not sure that we change session_id() at all. Session_id is the name of the session file, and session_name of the cookie that stores the session_id.
If you'd like to send server details to me at dave@interactivetools.com I can debug it for you.
Thanks!
Dave Edis - Senior Developer
interactivetools.com