Links being redirected in show all changes and edit screens
Pioneer42 said: The blue link edit and then show all changes as shown int he three other slides or richard micklewood. It happens everywhere, not just on some people. Browser is Chrome, and also tried on edge.0
Tom Huber said: This was previously reported several days ago. So far, no response from FS about the problem, which is often the case with issues of this nature. One of these times, the system will simply start working correctly.
It is not unusual for a bug to remain in the system until a weekend (or holiday) passes. I am sure that a significant number of engineers are working from home during the pandemic, but they may be waiting for the issue to be assigned.
I have seen the problem with both Chrome and Firefox on a Windows 10 computer, so it isn't a browser/operating system issue.0
Tom Huber said: The original discussion is from 6 days ago at https://getsatisfaction.com/familysea... where it was reported that the problem is also with Safari on a MacOS.0
Gordon Collett said: With the complexity of computer programming required for a site like FamilySearch that does so much and the requirement they set for themselves for the program to work on as many different computer setups as possible, improving the site must be a lot like testing a newly developed medication.
First it will be given to a few people just as a test for safety. Then it is given to a larger group of people to test for effectiveness. Then it is given to an even larger group of people to make sure nothing untoward shows up. All sorts of approval and monitoring and reporting have to be done at each step.
Then the medication is released on the market. Unfortunately sometimes, and all too often, an adverse side effect that only appears one in a million times doesn't show up until five million people have taken it. Sometime it can be addressed, sometimes the medication has to be taken off the market. Much new research has to be done to figure out why those five people reacted so poorly and it can't be done without studying those people.
As is the case here. It's inconceivable that FamilySearch would not have noticed something as obvious as those "See All Changes" links in the edit boxes not working properly as pointed out here and in other posts in the initial design and testing of the update. This isn't poor coding. It is unexpected results due to a rare confluence of unpredictable circumstances.
As pointed out on the other post discussing this issue, these links work just fine on my system and have since the update was released.
This is just a long winded way of saying, it's not the coding. It is the coding and your system configuration. FamilySearch cannot fix this if they have only half the information they need.
So when reporting this type of glitch, always report your computer type, your operating system and version, and your browser and version.
Recently someone reported a problem using the site and it turned out that the problem resolved when he turned off all the extensions he had added to the browser. So also report all the non-standard changes you have made to your operating system and browser.0
Paul said: It works fine for me in Firefox, but not (as you say) in Chrome. So definitely appears to be an issue with certain browsers.0
Tom Huber said: Absolutely, Gordon. We always should report the device (mobile or computer), operating system (iOS or Android for mobile devices), and browser if used.
In this instance, the problem impacts all operating systems and browsers on computers.0
Gordon Collett said: Not mine!0
Tom Huber said: Interesting. You are not experiencing the problem from an Edit screen, when you click on the Show All Changes (used to be Show History) link? What operating system and browser are you using?0
Gordon Collett said: Oh, dear. What have they done? I've never seen this before. I just tested everything I can and found this:
MacBook Pro (13-inch, 2017)
Processor: 3.1 GHz Dual-Core Intel Core i5
macOs Catalina version 10.15.4
Browswer: Safari Version 13.1 (15609.1.20.111.8)
Browser: Firefox 76.0.1
All the See All Changes links work perfectly fine and take me directly to the change log. Firefox just updated on me to 77.0 but things still work fine after the update.
iMac (21.5-inch, Late 2013)
Processor: 3.1 GHz Quad-Core Intel Core i7
macOs Catalina version 10.15.4
Browswer: Safari Version 13.1 (15609.1.20.111.8)
Browser: Firefox 76.0.1
the links go to the pedigree chart as others have reported here.
So it isn't a browser problem. I don't have any browser extensions I'm aware of but could that be the problem? It isn't an operating system problem. Is it an operating system extension problem? Either one that is present or one that is lacking? Please don't tell me it is a processor problem! Or an age of machine problem! Or is there a rogue version of the program out there that doesn't work properly and they can't figure out which server it is on to get it replaced with the correct version?0
Tom Huber said: Wow, that is strange. The OS and Browser are the same version, so something is sensitive to some other factor (possibly a BIOS issue -- and yes, those were very big issues back in the early days of personal computers. But this is some forty-plus years into that era, so BIOS issues should have been resolved.)
At least we know that this is a problem that FamilySearch engineers need to address and where the problem lies. We should not have to update any computer's BIOS to make something work in FS when all other factors are the same.0
gasmodels said: This feature seems to be changing daily. On my windows 10 machine. if I use Chrome I get the history of changes. If I use firefox or edge I get the pedigree chart. the browser versions are
Chrome --- Version 83.0.4103.61 (Official Build) (64-bit)
Firefox -- Version 76.0.1 (64-bit)
Edge -- Version 83.0.478.37 (Official build) (64-bit)
I'll try and check my laptop later and add that information.0
Tom Huber said: You are lucky. This may also be a BIOS issue on machines with Windows 10. I just checked and while the system starts to open (but not display any information or even title) a change log, it suddenly opens the pedigree view.
Version 83.0.4103.61 (Official Build) (64-bit)
Windows 10 is up to date (a Dell laptop).0
gasmodels said: I have exactly the same behavior on my windows 10 laptop. Chrome works as intended but edge and firefox do not show changes but instead show the pedigree.0
Jeff Wiseman said: Still not back to normal here. "See All Changes" under any event edit ALWAYS brings up a pedigree chart with the person in question at its root.
Model Name: iMac
Model Identifier: iMac17,1
Processor Name: Intel Core i5
Processor Speed: 3.3 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 6 MB
Memory: 8 GB
Boot ROM Version: 22.214.171.124.0
SMC Version (system): 2.34f2
macOS Sierra 10.12.6
As was mentioned before, it seems to begin to render a page for something, then that disappears and is replaced by the pedigree chart. This has been like this for at least a week now.0
Tom Huber said: I just ran into a very interesting situation: When I opened the change log from the profile's details page, the old interface (without any kind of filter button) was displayed. Chrome on Windows 10.
After opening the same record in Firefox, it displayed with the new interface. I went back to Chrome and refreshed the screen and the new interface was displayed, replacing the old.
Next, I checked the Show All from an edit screen, and it displayed the new interface with the filter set.
I may have hit a point in which the fixed code was being inserted into production, but for those who have experienced the issue with pressing Show All from an Edit screen resulting in a display of the Pedigree, please give it a try now to see if the fix indeed has been pushed to production.0
Jeff Wiseman said: I just tried the two configurations that I mentioned above and in both cases they still go to the pedigree screen...0
Tom Huber said: The system appears to be loading sensitive. I have experienced more problems with Chrome, but not Firefox, on my Windows 10 computer.
I resolved the issues by clearing history and cache images and files for all time, leaving cookies alone. Then I rebooted the computer and the results were a much faster load of FamilySearch, and no problems opening the change log from either the details page or an edit page.
If you are experiencing problems with any of the supported browsers, then clear the browsing history as well as the cache images and files for all time. See if that clears up the problem.
I'm thinking if this takes care of the problem, that we have a set of browsers that have the Bill Gates syndrome -- not being able to cleanly handle cache and memory (browser history).0
Jeff Wiseman said: For Safari, I purged all history. Then removed all bookmarks for familysearch.org
Tom Huber said: Can you or did you clear the cache?
That is where I got the idea when the "Checking Cache" appeared repeated in Chrome while attempting to bring up the new Change log. After clearing the cache, the effect was immediate: faster-loading pages, which gave me the idea this might be a time-out issue.0
Jeff Wiseman said: In Safari on the mac, I don't believe that there is a "Cache" control. I think it is included with the history function.0
Gordon Collett said: I think Apple must have decided Safari's cache should never be a problem. You can easily find where to clear website data and browser history. But unless the cache is cleared when the history is, and it may be, I have no idea, it looks like the only way to clear some type of cache is to turn on the developers menu under preferences.0
Tom Huber said: Since I do not have a Mac (only an iPad), I do not know all of the options available in Safari.
This site has information on emptying the cache in Safari: https://www.businessinsider.com/how-t...
Evidently you can set up a cache on a Mac using Safari, as well as turn it off and even empty it. See https://support.apple.com/guide/mac-h...0
Gordon Collett said: See All Changes links are working correctly for me today in both Safari and Firefox on my iMac desktop. So more progress was made in getting that strange bug worked out. Hope the links are working for everyone else now, too.0
Paul said: Confirmed using Firefox, as well as Chrome.0
Jeff Wiseman said: It appears to be working at present for me as well on both Safari and Firefox on macOS Sierra.0