Source Linker is now giving an error when trying to open a census record (Denmark)
I have been working on Danish records for years and usually the source linker makes it easy to connect these sources for people. Starting about yesterday, any Danish record source linker suggestions for 1916 and 1921 ( among a few others) shows a record link which looks good, but when clicking on it, it shows very briefly and then: "Something Went Wrong
Error loading source: /ark:/61903/1:1:Q2CC-998Q" and other times, if I try to get there clicking on the link in the left of the link (on the person's name), it says
"We're unable to show this record.This record can only be displayed on certain accounts. FamilySearch must honor the agreements we have with our partners, record owners, and internal policies."
I understand the restrictions placed on certain records, but these census records have always been available. I can get to them through the Danish national records ( but not as easily ) and through Ancestry.com, but it is much more difficult to link them if FamilySearch says it cannot be done after suggesting it.
I realize the amazing power of the source linker. There has got to be an enormous process to bring this all together. I just thought I would ask to see what might have stopped working in this case.
Answers
-
There is a new restriction of those Danish censuses. See this thread
0 -
I am getting a rash of this message for many sources now. What is going on?
Even Findagrav, Billiongraves, SSDI, World War II Draft cards
All have same message.
0 -
I have flagged @W D Samuelsen contact me please's post for moderator response.
0 -
@W D Samuelsen contact me please Please provide URL's or more details to give us a starting point to investigate. I am aware that Nebraska WWII Draft Registration records have been intentionally restricted. Have you encountered others?
0 -
SerraNola
Even Findagrave, Billiongraves, SSDI, World War II Draft cards, these are well known.
When I tried to attach, there's no way to get the url's you were asking for. Findagrave is now letting the links.
Not Billiongraves now, lately I tried to link only to get the message demanding I be a member of Billiongraves before allowing the source link.
0 -
@W D Samuelsen contact me please Here is an example of a record from Billiongraves. Are you able to attach it? https://www.familysearch.org/ark:/61903/1:1:QKD2-LQNK?lang=en
0 -
no problem linking but if you need to see image…
This is the infuriating response.
https://billiongraves.com/grave/August-O-Sasnowski/14545903/subscribe?utm_campaign=record-cta2
Get Access for FREE
Contribute 250 transcriptions or 500 photos to get full access to this record.Records Transcribed0/250Photos Taken0/500 Learn More
Get INSTANT access for just
$5.00 / mo
Billed Annually SAVE BIG with the Annual Subscription. 60% Savings!Sign up and get full access to over 170+ million records, exclusive content, and so much more…Login or register to get a discount
Compare Plans (long list!)
Findagrave don't require any of these Billiongraves stuff in order to see images and read.
Can't even see who in the families with such restrictions by Billiongraves.
This is something FamilySearch need to revisit the agreement in light of those crazy restrictions. Before this change, there were no such restrictions.
0 -
Yeah. I get the same thing. Not sure when they switched to subscription. 😕
0 -
@SerraNola Here is one from FindAGrave:
https://www.familysearch.org/ark:/61903/1:1:QK1V-5N58
Winifred Harriet Score Stallard
Find a Grave Index
Death: 30 August 1966
Burial: Nelson, Nelson, New Zealand
Birth: 17 January 1887
0 -
https://www.familysearch.org/ark:/61903/1:1:FG34-B5D
Quintilia Sophia
India, Births and Baptisms, 1786-1947
Weaker Hint
Child: Francis James Blundell
Spouse: Francis Horniblow Blundell
https://www.familysearch.org/ark:/61903/1:1:FG34-B58
Francis Horniblow Blundell
India, Births and Baptisms, 1786-1947
Weaker Hint
Child: Francis James Blundell
Spouse: Quintilia Sophia
https://www.familysearch.org/ark:/61903/1:1:FG34-B5Z
Francis James Blundell
India, Births and Baptisms, 1786-1947
Weaker Hint
Christening: 5 October 1834
Bengal, IndiaBirth: 27 July 1834
Father: Francis Horniblow Blundell
Mother: Quintilia Sophia
0 -
@W D Samuelsen contact me please when I use the URL without the tracking information attached to it (this is the tracking part /subscribe?utm_campaign=record-cta2)
https://billiongraves.com/grave/August-O-Sasnowski/14545903 BillionGraves lets me view the information without paying.
0 -
To all, CLICK on the image to see clear photo. That's what SerraNola and I are referring to.
0 -
Find a Grave memorial ID 282226130 citation:
- Find a Grave, database and images (https://www.findagrave.com/memorial/282226130/lewis_reginald-hobbs: accessed December 20, 2025), memorial page for Lewis Reginald Hobbs (19 Mar 1917–12 Mar 1992), Find a Grave Memorial ID 282226130, citing Akatārawa Cemetery, Upper Hutt City, Wellington, New Zealand; Maintained by NZ4ME (contributor 51337793).
https://www.familysearch.org/ark:/61903/1:1:X3TJ-4ZXB
Lewis Reginald Hobbs
Find a Grave Index
Death: 12 March 1992
Burial: Hutt City, Wellington, New Zealand
Birth: 19 March 1917
0 -
https://community.familysearch.org/en/profile/JulianBrown38
Lewis Reginald Hobbs hasn't been added to Findagrave database yet.
0 -
@W D Samuelsen contact me please You won't find the record if you do a records search for his name in the Find A Grave collection. Nevertheless, there is a dismissed hint attached to his profile (LTVC-MDS). This seems to be a common thread with these inaccessible records: the records are not accessible for whatever reason, but there are still hints attached to potentially-matching profiles. There has been a response by a moderator on another similar thread: In the Family Tree record hints when click sometimes display "We're unable to show this record...". This says that the hints will eventually disappear completely.
But the question that still remains is: Why are certain seemingly-random records from various collections restricted in the first place? For example, Find A Grave, New Zealand probate and passenger lists, India births and baptisms, etc., etc.
0 -
https://community.familysearch.org/en/profile/JulianBrown38
You attached Billiongraves one.
No mention of any source being declined. Not even Findagrave index.
If it is up to me I would NOT link any from Billiongraves until they change their restrictions. (Currently you can not see clear photo of any marker unless you pay to be member or do what they require you to do, see my earlier post about Billiongraves). Findagraves does not require you to do stuff Billiongraves requires.
0 -
@W D Samuelsen contact me please You are quite right about there being no trace in Lewis Hobb's profile's Dismissed Helps or changelog for that Find A Grave index source record. I saw that it had vanished when I looked after reading your latest post. I've delayed responding to see if the same thing might happen to a few other hints that I have dismissed because the records that they reference are inaccessible. I was thinking that maybe this disappearance is part of the cleanup that is reportedly going on to make the hints that refer to inaccessible records disappear (over time).
I have looked at all the profiles for which I dismissed hints over the past week. I have found that a significant number are in the same boat, namely, the hints have been dismissed, but they are no longer in the Dismissed Helps list on the respective profiles. Other dismissed hints are still in place in the profile, and the records are still inaccessible. So, I am none the wiser as to what is going on.
As far as I am aware, dismissed hints are not recorded in the profile's changelog (or at least any such entry is not visible to mere users). My evidence for the fact that I did dismiss the hints comes from Family Tree —> My Contributions —> My Changes. Each dismissed hint is recorded there as a Record Hint Rejected entry against the profile.
0 -
@SerraNola @JulianBrown38 Merry Christmas. Appears to me to be a big problem as users may never see that Record Hint again, thus defeating the purpose.
Each dismissed hint is recorded there as a
Record Hint Rejectedentry against the profile.0 -
Not surprised at all about dismissed hints. Knew about it for years, having already looked into that.
The only way a hint can show up is to accept then detach. No way I will accept any hint that is wrong for the person.
0 -
I understand the issue and support restrictions based on policies of the record owners. I guess the main issue is that the response is not a message saying the record is restricted, but rather that "Something went wrong," leaving a person to think that something like that might go away. The real answer is to say that the record is currently restricted and that it is available when the access request originates from a FamilySearch Center computer. - Joseph Buchanan
0 -
I have an issue with this "This record can only be displayed on certain accounts. FamilySearch must honor the agreements we have with our partners, record owners, and internal policies."
I have one profile being battered by a certain record despite the fact the record is already linked, even image is visible.
Historical Hints kept sending this one no matter what. (it is Belfast Books)
0





