Home› Welcome to the FamilySearch Community!› Ask a Question› Family Tree

Source Linker Problem

System
System admin
January 12, 2022 edited July 16, 2024 in Family Tree
This discussion was created from comments split from: Why has Source Linker suddenly stopped linking sources?.
0

Comments

  • KennethVarley1
    KennethVarley1 ✭
    January 12, 2022

    Source linker has stopped working in Firefox browser.

    It will work in Microsoft Edge

    0
  • PiperTWilson
    PiperTWilson ✭✭✭
    January 12, 2022

    @KennethVarley1 - The first thing I suggest is clearing your cache & restarting your browser. Also, make sure you're working with the most current version of Firefox.

    Let us know if that helps.

    1
  • Julia Szent-Györgyi
    Julia Szent-Györgyi ✭✭✭✭✭
    January 13, 2022

    As Piper said, when something works in one browser but not the other, it's usually fixable with some housekeeping in the "broken" browser. For some reason, FamilySearch is particularly prone to glitches or incomplete loads, which your browser "helpfully" saves and keeps serving up in the name of saving bandwidth. You need to tell it to get rid of the buggy saved files by clearing your cache and cookies. This should restore the functionality.

    1
  • RobinsonSonyaJohnson
    RobinsonSonyaJohnson ✭
    January 13, 2022

    I have an app that's supposed to clear cache/cookies at certain intervals, but it apparently quit doing its job! I had forgotten it. Firefox updated and now I manually clear the cache (which means I have to sign in again). Thanks for your replies!

    1
  • CraigBanker
    CraigBanker ✭
    February 4, 2022


    https://community.familysearch.org/en/discussion/comment/419853#Comment_419853

    Here are two related contrasting and reproducible cases.

    #1 - Using the latest clean version of firefox (96.0), attaching a source silently fails (with busy spinner and no specific error message presented on the client/ no timeout). The console contains many CORS errors.

    #2 - Using the latest version of BRAVE BROWSER (98.0/chrome based), the same operation worked. No CORS errors logged in the console.

    I gather that the latest release of firefox comes with enhanced security with respect to CORS and this may be related to the problem.

    Is there anyone that can kindly point this out to the developers? (Or direct me to where I can do the same...)


    --Craig


    #CORS#

    #SOURCELINKER#

    1
  • PiperTWilson
    PiperTWilson ✭✭✭
    February 4, 2022

    Mod Note: One duplicate post has been deleted.

    1
  • KennethVarley1
    KennethVarley1 ✭
    February 9, 2022

    Cleared cache & restarted as per PiperTWilson instructions.

    I have attempted one link, and it worked.

    Thank you very much. I was getting sooooo frustrated with it.☺️

    1
This discussion has been closed.
Clear
No Groups Found

Categories

  • All Categories
  • 42.7K Ask a Question
  • 3.3K General Questions
  • 570 FamilySearch Center
  • 6.7K Get Involved/Indexing
  • 640 FamilySearch Account
  • 6.5K Family Tree
  • 5.1K Search
  • 996 Memories
  • 2 Suggest an Idea
  • 473 Other Languages
  • 62 Community News
  • Groups