Error Toast when attaching a marriage event
When attaching a marriage event in the new Source Linker, I will always get an Error Toast that says "! Something went wrong. Try again later."
This happens on marriage events that I have added to a record. In the collection that I'm working on (Italian Birth Registrations), birth records often have marriage and death information added later in the margin. In the case of the marriage, adding the name of the spouse to the record, and then adding a marriage event, is the best way I've found to add this additional information to the tree with clear source information.
This used to work in the old source linker. I typically process several of these types of records every day. Once I switched to the new source linker, I get this error message. I can workaround this issue by adding the event to the couple directly in the person page and then coming back to source linker to complete the Attach. But then I'm typing in the marriage information twice which is both error prone and inefficient.
Here is a link to source linker for a case that I haven't done the workaround on. You can see that if you try to add the marriage information for Maria Driussi, when you click Attach, you'll see the error message.
https://www.familysearch.org/search/linker?pal=/ark:/61903/1:1:QVSW-X6SJ&id=GTYN-SJ7
Comentarios
-
I just tried it, and no error message. I've never had this particular problem, and I was doing a fair amount of taking Source Linker up on its offers, last night. (No Italian sources, of course, but actually several Viennese ones. Ack, that dratted handwriting.)
All I can think of is to try the usual song-and-dance (try it in a different browser; if it works there, make sure your original browser is up to date, and clear your FS-related cache and cookies in it).
(How'd you manage the screenshot? I'm still getting "permission problem" on copy-paste, and the Insert Media button expects a URL, which of course screenshots haven't got, not even if I save them as files.)
0 -
Thanks Julia. This happens for me on multiple computers and multiple browsers, and I've even cleared cache and cookies on one of those. So I don't think it's that.
Marriage events on standard marriage records work fine for me. It's just in the cases where I edit the birth record and add a spouse and marriage event using the marriage information annotated in the margin of the birth record. I used to do this all of the time successfully, but with the new Source Linker, I get the error.
Feel free to try this on the example record I provided. I'm fairly certain you'll see the issue. Just click "Attach" on Maria Driussi, click "Add" on the marriage record, and then click the "Attach" button.As for the screen shots, I used the workaround provided here:
1 -
I get those errors when more than one entry for the marriage exist, and you try to add the standardized place name. So there could be four or five marriage events, all detailing the same marriage on the same date, but the entry of facts varies. So let’s say one says the place in the stanardized format (dd/full month/year), and another is ddMMMYY, and you try o convert that to dd/full month/year, you get the error you wrote about because that fact already exists on another entry.
2 -
@monnettohio, that would make sense, if the profile already had an identical marriage event — but it doesn't (https://www.familysearch.org/tree/person/details/GTYN-66R). In fact, it doesn't have any events entered in the couple relationship section.
I've tried changing the date and/or the place on the Osso-Driussi marriage event in Source Linker, but it doesn't help: even if I try to move the wedding to Budapest, Linker comes up with the black message. There's something in this index that Source Linker is failing to deal with usefully.
0 -
@ShawnFReid Try this as an experiment. You might need a geek to help. Change your DNS server settings to avoid using the standard setting that relies on your router or ISP. Change your settings to use OpenDNS or G**gle's own DNS service. Write down what you've done so you can revert it all.
After making the changes, time how long it takes for the error message to appear. If it doesn't appear, then it's possible that your problem is a delay in name resolution that's causing a timeout in part of the FamilySearch deep down internals.
0 -
@Re Searching, the DNA server change made no difference. I still get the error. And as always, the error comes up pretty quickly, so I'm pretty sure it's not a timeout issue.
I've now verified this issue on multiple computers, multiple browsers, cleared cache and cookies, multiple signed-in users, multiple profiles, multiple buildings, multiple ISPs and now multiple DNS servers. So, I'm fairly sure it's not an environment specific issue on my side.
@Julia Szent-Györgyi was able to reproduce the issue (thanks Julia!). It would be great if one or two others could try this simple test.
Try this on the example record I provided. I'm fairly certain you'll see the issue. Just click "Attach" on Maria Driussi, click "Add" on the marriage record, and then click the "Attach" button. (I'll keep an eye on this record and if anything goes wonky while testing this, I'll make the corrections, but I doubt anyone can complete it without the error).
0 -
@ShawnFReid Yep, you're spot on. It happens when I try too, just as you describe.
Since she has no other sources attached, there's not a lot lost in attaching another person as spouse of Armellino Vincenzo Osso and then try the source linker again with that person.
UPDATE: Ok I tried that and it didn't work either.
ANOTHER UPDATE: I got it to attach by reverting to the record view, and then choosing Maria as the person of interest, and selecting the new Maria — https://www.familysearch.org/tree/person/details/GYQ1-PS8 as the target. All that remains is for you to merge that one with yours and you're up and runnign again.
0 -
@Re Searching Thank you for confirming the error.
I've made the merge as you suggested and put things back in a state where the error message occurs again.
My primary goal in reporting this error is to let the Source Linker Engineers know where something that was working before is now broken in New Source Linker. With multiple users confirming the error that I'm seeing, I hope that helps move this issue along to them.
2 -
I duplicated the problem and added it to the list for the engineers to review.
3 -
Today I went through multiple identical errors (at least 3-4) when trying to attach a marriage record to the second person of the two.
The latest error occured here:
Hope this is being worked on :)
0 -
Total inconsistency with this one. I just attached both the prime person and spouse without any problem, yet I have been getting the "Something went wrong…" message for several days now when trying to add the spouse under the exact same circumstances. The workaround is to move the spouse (usually wife) to be the prime person (click on Change Person and select), but I believe that loses the ability to move the date across during the procedure.
Will have to try move examples later, and hopefully provide URLs. Meanwhile, here's one that worked as with old source linker (although the same date / event was already inputted to their Couple Relationship areas): https://www.familysearch.org/search/linker?ark=/ark:/61903/1:1:66GN-X8WQ&id=L4GS-1G2&hinting=/tree/person/details/L4GS-1G2
There is perhaps an associated issue in that it appears individuals are sometimes being indexed twice - in this example, the wife as both Elizabeth Clayton and Clayton Elizabeth.
0 -
I was beginning to think the problem had been resolved, when I just now encountered the "Something went wrong. Try again later" message when trying to attach the Marriage Notice source to Eliza Nicholls - see https://www.familysearch.org/search/linker?ark=/ark:/61903/1:1:NX2M-KYH&id=M5P2-5MS&hinting=/tree/person/details/M5P2-5MS
Ah, now it's worked: when I didn't move the event data (Marriage Notice - Other Information) across. So is that what the new source linker is not liking?
Now I've just tried carrying across a Marriage record for Eliza (see https://www.familysearch.org/search/linker?ark=/ark:/61903/1:1:NX29-SL7&id=M5P2-5MS&hinting=/tree/person/details/M5P2-5MS ) and the Marriage data (goes to the Couple Relationship area) was carried across. Incidentally, this is where I was hoping the new source linker would not allow this to happen. There was already a source there (same date, but differently standardized location), so now there are two for the same event (see Eliza's profile at LYTS-9FW and open up the Marriage box).
I believe we should be prevented from carrying across multiple events for the Marriage via the source linker, in the same way we cannot do this for any of the other Vitals events: if there are two versions of an event only one of them can be added to the Details page, so why this anomaly relating to marriages?
0 -
@Paul W, as for your question on multiple marriages, there is a fundamental difference between marriages and the other vital event of birth and death. Someone is born and dies at most once, but they can marry multiple times. For example, in many parts of Italy during certain time frames, most couples had both a civil marriage and a church marriage. They usually happened a few days apart, but sometimes months or even years apart. They often took place in different towns. It's important to be able to record both of these events. (I wish there were multiple marriage types to allow us to indicate which type of marriage it was, civil or church, so I usually note it in the Reason field).
1 -
Thank you for your response. The problem with an enhancement like this (the NSL) is that it not only needs to be carried out in consultation with everyday users (where these Feedback groups have been an excellent way of getting our issues to the engineers), but in coordination with other FamilySearch teams.
For example, whilst I accept your valid point regarding marriages, once marriage data is carried across via the source linker, if it carries an earlier date it will automatically cause the existing data to be removed from the Details pages of the couple concerned - as the earlier dated event always takes precedence. If, as you suggest, there has been a religious and a civil ceremony, users have to delete the earlier event from the Couple Relationship area if they wish the later event to appear on the Details page. So, no, there is not currently a way to record all marriage events in the Couple Relationship area - that is, not until another FamilySearch team finally gets to implement the long-standing suggestion from users to have the ability to choose the item displayed on the Details page(s) from a pick-list, rather than having to delete the earlier dated event.
The continuing problems with carrying over items via the NSL also require liaison with FamilySearch teams responsible for indexing, as well as the "post-indexing" phase. Happily, one issue that has been resolved is in it finally being recognised that (infant) Baptism = Christening: thus a Baptism event now transfers straight to the Vitals section (as a Christening), instead of going across as a Custom Event and the Vitals field remaining empty.
Hopefully, all marriage related events (e.g. relating to banns, licences, etc.) are now being indexed as such, instead as simply appearing as "Marriages" (as was past FamilySearch practice. This caused, say, data relating to a marriage licence to replace (on the Details page) the correctly placed details of the marriage ceremony, just because it carried an earlier date.
I very much hope FamilySearch engineers are now realising the importance of not only working with us everyday users, but of collaborating with other FS teams: in order to sort out some of the problems we continue to encounter, in using the source linker and by other actions.
I have just requested an image to be attached here, which should illustrate the problem with the allowance of multiple marriage events being carried over in the source linker process. Hopefully to follow soon!
0 -
Thanks, @Paul W, for the additional detail and clarification. Yes, I've wished that I could, as a minimum, select the "preferred" marriage event to show up on the details page as opposed to the earliest dated event.
I was extremely happy to hear about the Baptism → Christening development as it will avoid so many problems that I've had in some of my Argentine lines.
0 -
BTW - I just checked through all those events that had found their way onto the Couple Relationship page(s) and found the top one related to the civil registration of the marriage and three other sources related to Banns, all of which had been indexed as if they were for the actual marriage event. I had to delete all four in order to get the actual marriage ceremony event (for 7 December 1883) displayed on the Details page(s)!
Thankfully, banns and licence events are nearly always indexed as such nowadays, so fewer examples like this should be found in the future.
Thank you for giving this matter your attention and for your understanding.
Paul
0
