Index corrections are broken!

LegacyUser

Juli said: I just tried correcting an index entry and failed: I can zoom in and out on the image, but I cannot pan, and I cannot draw a box to highlight anything.

I have the same problem in Firefox 78.0.1, Edge 44.18362.449.0 (pre-Chrome-clone), and Edge 83.0.478.58. This is in Windows 10.

LegacyUser

Tom Huber said: This showed up before as a problem, not long after the indexing feature was first introduced. Some update broke the system again.

LegacyUser

Jeff Wiseman said: Juli, I ran into this about a week ago. I fiddled and fiddled and fiddled with it and it was just brain-dead to some mouse operations.

So I just shut everything down. I went back in, and it actually worked. It's like something in some internal browser cache got hosed and couldn't self correct itself.

I haven't seen it since, but I've not needed to use it.

LegacyUser

Juli said: Some internal browser cache on what amounts to three different browsers, though?

It's still doing it for me: no response to any mouse input on the image portion of the screen.

LegacyUser

Jeff Wiseman said: Good point. And that IS the same behavior I observed.

LegacyUser

Juli said: I just discovered that the image portion of the screen *does* respond to touchscreen input. I haven't tested with a touchpad yet.

LegacyUser

Juli said: Drawing highlight boxes with one's fingertip is Hard.

LegacyUser

Beth Ann Wiseman said: This should be fixed now and was only an issue with touch screen machines.

LegacyUser

Juli said: Nope. Memories tagging works, but index corrections continue to not react to mouse input. I can zoom in or out with the mouse wheel, but panning and drawing/editing highlight boxes requires a finger on the screen.

LegacyUser

Jeff Wiseman said: Same thing today. I cannot correct what is some seriously error index values (e.g., birth dates being marked as 2017 when in fact they are 1900, etc.)

You can enter the new value, and you can select the reasons and enter the optional note, but you cannot highlight the affected area AND THE SAVE FUNCTION will not work--end result, nothing gets changed and you've just wasted your time.

I have noticed some thing also that may have something to do with this. This is happening on indexes that are also associated with the schizoprenic citations where the update of the persistent ark type URLS failed (I am STILL seeing these things all over the place. with their corresponding duplicates). These indexes also have all of the garbage dates in them. Also note how the indexed dates are ALL wrong. See:
https://getsatisfaction.com/familysea...

If you look at the image for item #4 in my post about half way down the topic, you can see the Birthdate of the groom is listed as Apr 1929 with the alternates being 1829 and 0029. The spouse's is May 2002 with the alternates being 1902, 1802 and 0002. But if you look at the event date for the marriage, it is 1 Oct 1905. The fact that absolutely NONE of those "indexed" dates are anywhere NEAR being close to what they should be may have something to do with why the system fails when you attempt to correct them.

Also this Predominantly appears to be associated with Marriage records. At least that is the only place I have been seeing it recently. All of the corrupted ark URL type index citations are also the ones where this is showing up. It all appears to be one big issue related to the failed ark URL updates, and the associated damaged citations that are now left laying around.
https://getsatisfaction.com/familysea...

LegacyUser

Slotbuddy said: I still cannot highlight at times; one of those things where sometimes it works and sometimes it doesn't. I always use the same browser (Chrome) since Firefox last crashed and I gave up trying to restore it. When it "feels" like working, it will make the corrections easily, but when it doesn't "feel like it", I just save the correction until the day it is in a better mood. Not worth getting myself agitated trying to get it to work.