Odd glitch with Ancestry tree maps

[Galium]

I have emailed them.  Perhaps they need more people to point it out; we can't be the only ones, and I've never had this problem before.

[Flemming]

I have emailed them.  Perhaps they need more people to point it out; we can't be the only ones, and I've never had this problem before.

Just wonder if you've had a reply. No sign of the issue resolving here.

[Galium]

Yes, I did get a reply. Unfortunately the response seemed to be designed to help someone who was having problems getting their own map to show the proper locations, so I suppose I didn't explain things well enough.

I have replied.

[Flemming]

Any progress? I tried again and got a more helpful reply and have sent more info. Also tried it on an iPhone and it's the same issue, and the phone then crashed as well.

Happy days.

[clayton bradley]

I'm having the same problem too. Lower numbers open easily but the higher numbers won't split as they used to and I haven't changed anything. cb

[Gadget]

I don't see any pattern in what opens and what doesn't. The last time I looked I found that  if I zoomed in to a cluster (say around London) and they still overlapped at the  2-3 level, I could only open the one(s) on top.   This doesn't always happen  but I'd be interested if anyone else has had this with an overlapping  grouping.

[Flemming]

Just had the same old reply. It's my fault for using the wrong browser and, if I try another one, it will all magically resolve. They've accessed my account using Chrome and say all is well, but Galium has had issues using Chrome (and Firefox, which Ancestry also suggests) and so I don't see why it would be any different for me.

They also say this:

If you can try to access your account on another device or web browser this should resolve the issue for you.

I did try another device and the website crashed it, but that seems to have been overlooked.

I'm having the same problem too. Lower numbers open easily but the higher numbers won't split as they used to and I haven't changed anything. cb

This is what gets me, too. We don't make any changes to our settings and yet something stops working. It can only be Ancestry or the browser but, if people have the same issue using different devices and browsers (which we all probably are), then it goes back to Ancestry making changes.

I just get the feeling they really couldn't be bothered.

[gizmo303]

Yes this happens to me.

I doubt it's a browser or cache thing. It's more likely Ancestry tinkering with things when they should leave it alone.

The people in customer services are probably unaware what's going on at that level.

[Flemming]

Just when I thought we were getting somewhere, Ancestry replies with the following...

Have you tried to use Google Chrome? The option should of course work on all browsers and devices but we want to make sure if the issue is on the users´ end or ours, as it is currently working for us.

Do you think they sit around drinking coffee and laughing at us?