Preferred relationship is stuck on wrong relationship
kwc2-gtb has two marriage relationships. One marriage is to kwc2-gty which is to my biological grandmother. The other relationship is to l8b7-z4p which is a step grandmother. I would like to have the marriage to kwc2-gty be the preferred marriage but is stuck on the other marriage and will not change even after following several steps tried with the assistance of a missionary at the SLC familysearch library.
Answers
-
setting a preferred person’s preferred spouse does not change the preferred parents of that person’s children.
Looking at the tree, preferred parents for KWH5-62B are KWC2-GTB & L8B7-Z4P
Preferred Spouse for KWC2-GTB is KWC2-GTY
0 -
"Preferred" is a per-user setting. In other words, it doesn't matter what any of us see -- that's just the default (whatever that is).
I don't think Rudolf Jr.'s preferred parents have any bearing: for me, it's defaulting to Martha as Rudolf Sr.'s preferred spouse, while Rudolf Jr.'s preferred parents are Rudolf Sr. and Kunigunde.
It seems more likely to be an over-helpful browser: it's trying to save you time and bandwidth by serving up an old, stale version of the page instead of going and fetching a fresh one. The easiest way to check if this is the case is to open the page in a different browser.
0 -
I too am having problems with the "Set Preference" for spouse. It is stuck. I was able to change the preferred spouse before the last update to FamilySearch and it would reflect on the fan chart. I contacted the Family Search Missionaries twice and they do not know why the preference is stuck. I was told to post here in hopes that the web programmers would see the posting and schedule a fix. Otherwise, any suggestions?
0 -
I see no evidence of any general problem with "Set Preferred" allowing me to set a preferred spouse. I'm able to change a preferred spouse, and that change becomes effective; I change it to a different spouse, and that change is effective, both on the person page and on the fan chart.
So either there is a misunderstanding about how this feature works, or there is some relatively rare problem related to a particular person in the Tree or the browser environment being used.
Could you provide more details about the steps you are taking, and what you are seeing that doesn't match your expectations?
0
