Caution when Using Beta FamilySearch
I have seen it mentioned, but in answers and not as a topic.
Use caution when wanting to use Beta FamilySearch. If you use the same browser, cookies seem to be shared somehow and you can make changes in the tree that also show in Beta FamilySearch. The solution we have found is to either use a different browser when using Beta, or open an incognito window.
Freaked me out when I saw a record error in Beta, and then corrected it in the real tree, and when I went to Beta, it was also corrected (or actually gone like it never existed)!!! There was nothing in Latest Changes either. They should not be connected like that!
So, just an FYI and hopefully helpful tip.
Answers
-
What sort of a record did you correct in FS proper? A person's profile or an index record?
It is possible to set up a Beta type scenario with layered data so that the top layer in Beta is initially empty, the "normal" level below, and any updates made in Beta are put into that top layer, leaving the "normal" data untouched. Record access from Beta looks first in the top layer and, if the record isn't there, it looks through to the "normal" layer. This means that any update made in "normal" will be seen in Beta if Beta hasn't already created its own copy.
I'm not saying that explains what you saw, just that it is a possibility - we did it on our mainframe system years ago.
Incidentally, I have used a separate browser for Beta for years but I've forgotten if there was any particular reason for me doing so, other than it being more obvious which window was which. Maybe separation of cookies had something to do with it???
1 -
The reason I have always used a different browser when using the Beta version is that I found it impossible to switch between the two versions without being crashed-out of one.
Maybe there has been a change whereby one can now work in both whilst using the same browser, I'll have to test later. If so, maybe the previous behaviour was to prevent issues arising, like the one being described here.
0 -
There was a duplicate record I wanted to keep in Beta for training purposes. I thought I could safely return to the FamilySearch tree to correct it, and beta version would remain. Nope!
So I opened a different browser, searched high and low for another duplicate record, and this time I could keep beta version AND correct duplicate.
More an inconvenience than anything and not a big deal unless you’re wondering why beta is changing on you live!
Thanks for the replies!0 -
Are you talking about CETs? If so this discussion probably would be better served in the CET Feedback group. The questions will reach the engineers at that location better.
1 -
Collaborative tree FamilySearch vs. Beta FamilySearch.
0 -
Sorry….
0
