Errors when clicking user profile names
In the FamilyTree website, I can click on user profile buttons to display information about the user or initiate a chat, etc. In the last couple of weeks, I have found that if I click on buttons relating to a user more than once on the same screen, a small user information dialog opens briefly then disappears and an error toast flies out at the top right of the screen "! Unable to read contact information. Please try again later.". I can try again immediately and the dialog opens properly. The error happens every second time that I click on any button on the screen that relates to that same user. It happens independently in the same fashion for buttons relating to other users.
This appears to be the result of failed caching or retrieval of user information. The functionality is failing its most basic test; to retrieve the user information that has been cached (preferably more quickly and without having the dialog open in one position and then jump to a position closer to the clicked button).
This happens in the main profile page and in the dialogs that are used to edit vitals and other information. One place where there are no errors is in the Following list. In that screen, the caching seems to have been implemented successfully (or has not been broken). As expected, the first click on any button for a user is slower to respond than subsequent clicks for that user.
Answers
-
@JulianBrown38 Have you seen this thread? You may have encountered some of the same issue mentioned here. As Rhonda mentions, there is a ticket for a fix.
0 -
Thank you for pointing this out. My issue may well be related in a perverse sort of way. The error message that I see is the same as the one that occurs in the new change log screen when I click on an Unknown Contributor. The odd thing is that I can't reproduce my problem when I click multiple times on a real contributor in the new change log. (That makes 2 places where the process works correctly.)
I think that the current change log was where I first encountered my issue. Maybe the bug hasn't been implemented in the new version yet.
1
