More strange action with the change log
LegacyUser
✭✭✭✭
Tom Huber said: The change log has started to behave even stronger than mentioned in several other message threads.
This one involved Chrome on a Windows 10 Dell Laptop:
The change log is reached from the person's profile details page:
When I clicked on Show All, the following page appeared (Note that this is the old UI for the change log, minus the filter option):
I refreshed the screen several times and still the system displayed the above. Finally, I closed the screen and reopened the change log via the Show All. Now the screen shows this:
I had rebooted the computer just before I started working with this record. I wanted to see if the redirect from an Edit screen goes to the profile or not (It still does with this computer) with a much smaller change log -- the other that I had been trying was Pieter Claesen with its pages of change log, so my conclusion after completing the comparison is that the size of the change log doesn't matter. The redirect from Show All Changes on edit screens is still a problem with Chrome on this computer.
The strange action noted above happens only after I reboot my computer.
This one involved Chrome on a Windows 10 Dell Laptop:
The change log is reached from the person's profile details page:
When I clicked on Show All, the following page appeared (Note that this is the old UI for the change log, minus the filter option):
I refreshed the screen several times and still the system displayed the above. Finally, I closed the screen and reopened the change log via the Show All. Now the screen shows this:
I had rebooted the computer just before I started working with this record. I wanted to see if the redirect from an Edit screen goes to the profile or not (It still does with this computer) with a much smaller change log -- the other that I had been trying was Pieter Claesen with its pages of change log, so my conclusion after completing the comparison is that the size of the change log doesn't matter. The redirect from Show All Changes on edit screens is still a problem with Chrome on this computer.
The strange action noted above happens only after I reboot my computer.
Tagged:
0
Comments
-
Tom Huber said: I just went through and rebooted my computer and then tried the same thing with Firefox. Everything worked correctly, including opening the new change log from the details page and opening a filtered change log from an edit screen.
I'm going to test this same system, but after I clean up any add-ons and extensions in Chrome.0 -
Tom Huber said: First -- I have resolved this issue.
For me, this was a Chrome issue. After trying several different approaches, none of which provided a satisfactory solution, I clear the browser's history and cached images and files for all time. It took a long time to complete the action. I did not touch the cookies history.
Then I rebooted the computer. I opened FamilySearch (it was faster loading than before), and opened up the same profile I had been testing. Opening the Show All on the change log from the details page resulted in a clean display of the new user interface. Going to the Edit screen and using Show All Changes opened the new user screen with the appropriate filter.
So, if your copy of Chrome is giving you fits, Clear the history and cache for all time and see if that fixes your problem with the change log.:0 -
Tom Huber said: I may have spoke too soon. I just did the same test with Pieter Claesen 9312-XFX and when attempting to open the change log from an edit screen (I used name since it gets changed periodically to include the Wyckoff surname), the system started to open what appeared to be the old change log, then after waiting for some time, it opened the pedigree chart.
However, when I tried it again, it opened the new change log and continued to do that from there on.
The Engineers should look at the load time for change logs that have a lot of entries. Once they are loaded, they appear to work correctly, but otherwise, the page defaults to the pedigree view (which it should not do).
So, while the workaround is to clear the browser's history and cache, the issue may be a timeout because of a long load time to bring down a huge log to the local computer. A different approach may be needed, particularly for areas where the users are adversely impacted by slow internet (backbone) speeds.0 -
Heidi Kuosmanen said: Thanks Tom about this message. I also noticed old change log on some persons. I use newest chrome browser. After I cleared the browser's history and cached images and files for all time and rebooted the computer, I got the new change log.0
This discussion has been closed.