Page 1 of 1
FH Version 7.0.8.2 and FMP Hints
Posted: 04 Oct 2021 10:05
by janew
When I started up Family Historian today it prompted me to download the latest version 7.0.8.2 which I did and since then my FMP hints have stopped working but MyHeritage hints are OK. I have a subscription to Findmypast.
When I click on the number of hints for FMP it says “loading hints”, takes some time and then the helpful message “Oops, something went wrong… Please try again later” appears.
I have tried with Web Search Window and External Web Browser for the location and the same thing happens each time. My default browser is Firefox.
After I have tried to access the FMP hints and fail they disappear and I can’t make them reappear so I won’t be able to find out what the hints were.
How can I get back to the previous version of Family Historian where my FMP hints worked?
Re: FH Version 7.0.8.2 and FMP Hints
Posted: 04 Oct 2021 10:19
by ColeValleyGirl
Before you revert, let's try to fix the problem. Can you try clearing all your FMP cookies in the internal and external web browsers, and report back please.
Re: FH Version 7.0.8.2 and FMP Hints
Posted: 04 Oct 2021 10:24
by janew
I did that already!
Re: FH Version 7.0.8.2 and FMP Hints
Posted: 04 Oct 2021 10:37
by RS3100
I am seeing the same problem this morning, although still on 7.0.7. The error message alternates between the "Oops, something went wrong" message, and a 400 error, "bad cookie header", both in the internal and my external browser (Chrome). I've tried deleting all cookies from Chrome, but I don't know how to delete them from the internal Edge based browser?
But since trying to access a few FMP hints for various individuals, all of the FMP hints have disappeared from the focus window and I'm just getting a "Find my Past searching..." message when I hover over the hint icons, which never completes.
Re: FH Version 7.0.8.2 and FMP Hints
Posted: 04 Oct 2021 10:38
by ColeValleyGirl
Thanks for providing that information.
I have had hints working since I've upgraded to 7.0.8.2 but they aren't working today -- I wonder if it's a FMP issue?
I suggest logging it with the Calico Pie support desk. Within FH, click Help > Technical Support and scroll down to the bottom to find the link to contact them.
Re: FH Version 7.0.8.2 and FMP Hints
Posted: 04 Oct 2021 10:45
by janew
Thanks - I'll raise it with Calico Pie and hope to get hints back soon!
Re: FH Version 7.0.8.2 and FMP Hints
Posted: 04 Oct 2021 10:50
by ColeValleyGirl
Let us know how you get on?
Re: FH Version 7.0.8.2 and FMP Hints
Posted: 04 Oct 2021 10:52
by janew
I certainly will...
Re: FH Version 7.0.8.2 and FMP Hints
Posted: 04 Oct 2021 11:38
by AdrianBruce
According to my Facebook feed, FMP were doing some planned maintenance work this a.m. "Apologies for any inconvenience caused..." it said.
Re: FH Version 7.0.8.2 and FMP Hints
Posted: 04 Oct 2021 11:41
by Jane
BTW If you have errors in a web browser window or web browser the problem is not likely to be be Family Historian, but with the web site you are visiting. So in general you need to copy the web site support and not Family Historian support.
Re: FH Version 7.0.8.2 and FMP Hints
Posted: 04 Oct 2021 11:46
by janew
I just had a reply from Calico Pie Support:-
"This message is most likely coming direct from the Find My Past web site, if possible please check with them."
It looks like others are finding the same so I guess it must be FMP at fault. I might try ringing FMP who are usually quite helpful.
Re: FH Version 7.0.8.2 and FMP Hints
Posted: 04 Oct 2021 11:54
by ColeValleyGirl
I suggested CP in the first instance as the FMP website is working fine for me, including tree hints, so it looks like an issue with the API that FH uses.
Re: FH Version 7.0.8.2 and FMP Hints
Posted: 04 Oct 2021 12:23
by RS3100
FMP website working fine for me too when accessed directly. I fired up my laptop which also has FH 7.0.7 on it and I'm getting the exact same symptoms as on my desktop with FMP hints, so agree that it looks like a FH/FMP issue rather than a local computer problem.
I've occasionally experienced similar symptoms before, and always found that I could get around them by deleting the second half of the URL displayed in the browser address bar, which starts with "partnerId=" and reloading the page request. But that's not working this time.