Skip to main content
J
JL-Schwab
Participating Frequently
August 13, 2015
Question

"Inheriting" Shared Objects (Flash Cookies)?

  • August 13, 2015
  • 1 reply
  • 557 views

Had a recent situation where our client wanted to update content in a Captivate module, republish, and promote to the production server. During testing, I noted that the updated .swf, wasn't inheriting the Shared Object data from a prior session with the previous content version.

Further testing with a new/bare-bones file was inconclusive concerning Shared Object inheritance.

So the question is this... can/will a revised version of a Captivate project inherit the Shared Object data from a previous version of itself given the same exact name, file location, etc? Doesn't appear to be so, I there doesn't appear to be the capability to retrieve the data like I can in Flash/Flash Builder with AS3.

In our case, it was the EXACT same file. There were just some minor text edits.

This topic has been closed for replies.

1 reply

TLCMediaDesign
TLCMediaDesign
Inspiring
August 17, 2015

It should, especially under your circumstances. Can you look at the SO and see if it's being updated? I think modern browsers are starting to not like SO's.

You might want to change to localStorage.

J
JL-SchwabAuthor
Participating Frequently
August 17, 2015

What's the difference between a SO and localStorage?

RodWard
Community Expert
RodWardCommunity Expert
Community Expert
August 18, 2015

SO stands for Shared Object.  It's Flash Player's version of a cookie.

Local Storage is what browsers now use as a way for HTML5 content to store some data that can then be retrieved in another session, i.e. just like cookies, but with more scope.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices