(Aug 21st, 2009, 8:07 PM)Ben Wrote: One thing to check: look at your database through phpMyAdmin or something like that & look for non-finalized submissions. If sessions are timing out you should see old unfinalized submissions in your form table that match the submissions that only have pages 6 & 7. In other words, look for submission IDs that are slightly lower (by say 1-5) than the submissions that have only 6 & 7 filled in. If you can see information for a single submission spread across two submission IDs, then yes, it sounds like sessions being emptied is at fault.
Good call...that is exactly what I'm seeing in my database.
When I look at the sessions table in my database, I don't see anything new created when I start filling out a form.
Started looking at this function in api/api.php
PHP Code:
/**
* Initiates sessions. The session type (database or PHP) depends on the $g_session_type var
* defined in the users config.php (or default value in library.php);
*/
function ft_api_start_sessions()
{
global $g_api_header_charset;
session_start();
header("Cache-control: private");
header("Content-Type: text/html; charset=$g_api_header_charset");
}
How does it depend on the $g_session_type var? Looks like it should really just include the code in session_start.php