SCORM 2004 Bookmarking issue with new update

Report · Jul 22, 2016

My team has spent countless hours trying to find a hack, fix, or solution to what we are currently experiencing. So, without further ado....

**Scenario 1 (Issue - browser not closed)**

User 1 logs into our LMS and launches a Captivate 9 (after April /May 2016 version) HTML5 course for the 1st time and watches 5 pages. User 1 then logs out, BUT they do not close the browser. User 2 logs in and launches the same course for the 1st time and the course pops up the Bookmark option to go where the left off. The issue is that User 2 should have been taken to page 1 without a popup. All browsers act the same way.

**Scenario 2 (No Issue - browser closed)**

The same as above, but User 1 shuts down the browser forcing User 2 to open a new browser session. User 2 does not experience the bookmark issue (clean slate).

**Scenario 3 (No Issue - browser not closed or closed)**

User 1 logs into our LMS and launches a Captivate 8 or 9 (pre April 2016 version) HTML5 course for the 1st time and watches 5 pages. User 1 then logs out and either close or do not close the browser (makes no difference with older Captivate). User 2 logs in and launches the same course for the 1st time and the course launches without the bookmark popup.

**Things we have tried**

We updated our logout functionality to try to force a session destroy and to kill any cookies. This has resulted in a new session ID for every logged in user, but does nothing for the "cached" bookmarking issue. Code that we have used is below. Is there anything else that we are missing or way to enforce Captivate to not look at a local bookmarking variable or cache and look strictly at the LMS cmi.location data in the database?

*************************************

// Initialize the session.
// If you are using session_name("something"), don't forget it now!
session_start();

// Unset all of the session variables.
$_SESSION = array();

    // If it's desired to kill the session, also delete the session cookie.
    // Note: This will destroy the session, and not just the session data!
    if (ini_get("session.use_cookies")) {
        $params = session_get_cookie_params();
        setcookie(session_name(), '', time() - 42000,
            $params["path"], $params["domain"],
            $params["secure"], $params["httponly"]
    );
    }

// Finally, destroy the session.
session_destroy();

*************************************

Report · Mar 27, 2023

I typo'd the document.cookie line, it should be:

if(nameless !== false) {
    document.cookie = name+";expires=Thu, 01 Jan 1970 00:00:00 GMT";
}

Report · Aug 09, 2016

Well, Adobe released a new update to Captivate and it did not address the issue above. Apparently it will require LMS providers and content developers across the world to report this same issue if their end users use shared environments and have difficultly getting them to close the browser after they logout. It's a shame that we now have to hack systems because Adobe changed how they lookup the bookmark location in SCORM courses. I guess it may be time to take that jump to Storyline as our primary tool and put Captivate to bed........