Skip to main content
Participant
January 6, 2017
Question

Flash player's compatibility issues to the earlier versions

  • January 6, 2017
  • 1 reply
  • 413 views

          When installed educational programmes like Oxford Directions Itools software,the audio records don't play the scripts don't show in the app. The only solution is to remove the latest Adobe flash player (e.g. ver 24) and to install ver. 17. Why does this happen? And is there any other way to solve this issue?

    This topic has been closed for replies.

    1 reply

    jeromiec83223024
    Inspiring
    January 6, 2017

    We made a change recently to how Flash content run from the local filesystem behaves by default.  My guess is that this is what you're running in to. 

    Disabling local-with-filesystem access in Flash Player by default

    Beginning with Flash Player 23, local-with-network permissions will now be applied to all local SWF content, regardless of the preference chosen at compile time.

    Background:
    When playing Flash (SWF) content from local filesystem, developers have historically been able to configure content to exclusively read from the filesystem, or communicate to the network. When this functionality was introduced over a decade ago, it enabled an interesting array of use-cases ranging from simple games to interactive kiosks. In context of modern web security, we believe that it is time to retire local filesystem functionality in the browser plugin. At the same time, Adobe AIR has been established as a robust, mature solution for delivering ActionScript-based content as a standalone application.

    Vast majority of Flash Player users and content will be unaffected by this change. This change only impacts Flash content played from the local filesystem, using the browser. Flash content hosted on the internet and local webservers, as well as the Standalone Flash Player remains unaffected.If you are a user who requires this functionality, these files can be added to the list of Trusted Locations in Flash Player.

    Workarounds for Legacy Content:
    We highly recommend that you only circumvent these controls to enable content from sources that they trust.

    For Individuals:
    For Internet Explorer, Edge, Firefox, Opera and Safari:
    On the affected system, go to the Flash Player Settings Manager:
    • Mac: System Preferences > Flash Player
    • Windows: Control Panel > Flash Player
    Select the Advanced tab
    In the Developer Tools section, click the Trusted Location Settings button
    Click the "Add..." button and add relevant files and folders to the list


    For Google Chrome (and other PPAPI browsers):

    Navigate to the Settings Manager page
    Choose Edit Locations > Add Locations from the popup list
    In the text field that appears, type or paste the file/folder path that you'd like to trust
    Click the "Confirm" button
    Note: Please be aware that the "Browse for files" and "Browse for folder" buttons do not function properly. You must manually type or copy/paste your path into the text field above the buttons to add the file or folder to the trusted list.

    For System Administrators:
    The legacy behavior can be restored by applying the EnableInsecureLocalWithFileSystem=1 flag to mms.cfg.

    Participant
    February 9, 2017

    I did as you explained. But it didn't solve the problem.Nothing changed. It's the same. So I turned to Flash player v22 again.

    jeromiec83223024
    Inspiring
    February 9, 2017

    Yeah, I just took a guess based on the available information.

    Some additional details would be useful:

    https://forums.adobe.com/thread/1195540

    The best way for me to figure it out is just to try it for myself.  If you can point me to a trial for the affected software or something, that would be useful.

    Thanks!