Home› Welcome to the FamilySearch Community!› Ask a Question› Search

Problem viewing sources

Options
  • Mute
Anna_Masus
Anna_Masus ✭
January 2, 2024 edited September 30, 2024 in Search

I have problems opening and viewing different record images. A few weeks ago this was not a problem. Now I get the following message:

image.png

It has been this way for about a week now. I have tried using different devices and logging in from different browsers.

image.png

image.png

The problem applies to all records.

0

Answers

  • Maile L
    Maile L ✭✭✭✭✭
    January 3, 2024

    Hi. We need more specific details to see if we can recreate the problem. Have you cleared you cookies and cache? Please provide what browser(s) you have tried and what operating system you are using. Are the browser(s) and OS updated? What steps do you take to end up where you are?

    0
  • Re Searching
    Re Searching ✭✭✭✭
    January 5, 2024

    This is the gist of a comment I added to a different question yesterday, but after of lot of trying, I can't find the thread today.

    I have noticed the image viewer presenting the error message as shown by the OP. The message will show up even though the image loads and displays correctly. But once this message appears, even if you clear it by clickng the X, it will always reappear when navigating through the images, even though the images still load properly.

    If you try to use the image viewer in a new tab or window, or using a different collection, the image viewer will fail to display anything.

    My thoughts are that the error detection mechanism is flawed, and it frequently makes false detections. But once it determined that it has detected an error, a flag is set which cannot be reset by loading an image correctly. In practice this flag cannot be reset except by clearing all stored data and starting againg from login. This is not good. If the image loading process succeeds, then the error flag should be cleared automatically. it would be better if it simply offered up the popup warning message and did nothing else.

    Personally, having seen the number of workarounds that have been included in the code, I think it would be better to remove the error detection routine completely. At least then I would be able to continue after errors without having to start again from scratch.

    0
  • Alan E. Brown
    Alan E. Brown ✭✭✭✭✭
    January 5, 2024

    I believe the comment you were looking for is here: https://community.familysearch.org/en/discussion/comment/538586/#Comment_538586

    0
This discussion has been closed.
Clear
No Groups Found

Categories

  • All Categories
  • 43.3K Ask a Question
  • 3.4K General Questions
  • 576 FamilySearch Center
  • 6.8K Get Involved/Indexing
  • 653 FamilySearch Account
  • 6.6K Family Tree
  • 5.2K Search
  • 1K Memories
  • 2 Suggest an Idea
  • 480 Other Languages
  • 62 Community News
  • Groups