Error message when I try to Search Records
I have been getting a error message that begins with "Oops, something went wrong" and no matter what I do I am still unable to search. this has been daily for the last 10 days or so.
Funny thing is I can search on my iPad fine. the trouble is on my iMac.
Anyone help solve this issue?
Answers
-
I don't have a solution but seconding this issue. For me the problem is on my MacBook but working fine on my iPhone. I'm using a safari browser in both instances (v.16.2 for Mac and v.17.6.1 for iPhone).
I'm getting the error message for both record and catalogue search, whilst Tree and Books functions are working fine.
I can't find any information on what browser versions are supported/compatible but, as a lot of the website is working fine, I'm not convinced its a browser issue. I've cleared cookies, but that hasn't helped either.
Hoping someone can shed some light for us!EDIT to add: I did just find that the website supports current OS one one back. So it may be an issue of older browsers functionality dropping off after all?
1 -
@Historical Interpretor @RaniM I reached out to engineering and received this message:
We had an issue with Safari 16, they stopped supporting something. We made a fix that I think was released today. Can you have them re-test? If that is not it, have them try a “New Private Window” to see if that changes things. It will turn off their browser plugins and cache so they start clean.2 -
I was searching earlier, but can't now. I have tried on Chrome and DuckDuckGo.
I tried in-private browsing. Still no luck.
"Oops, something went wrong"
0 -
it seems lots of people are having trouble searching and are receiving oops something went wrong error messages.
Not sure what else to do to solve this issue. I might be looking at purchasing a new iMac this year. Mine is from 2013!
2 -
@SerraNola Thanks for following up on this issue, its much appreciated!
I think the fix has mostly worked. In Search the sidebar search menu is now showing up every time, which it wasn't at all previously. I was still getting the error message on results at first, but after refreshing the page a number of times this seems to have come good and results are showing fine now, including selecting and viewing individual records. (fingers crossed this stays resolved!)
I can search the Catalogue fine now also, including viewing individual entries. However, when it comes to viewing image groups via those entries (per image below), I'm still getting the "oops something went wrong" message. Interestingly, I'm not having a problem viewing images in the image viewer via records search.
Browsing in a new private widow doesn't seem to make a difference to this.
Family Tree> Find is also working fine again today, where it was having issues before.0 -
@Historical Interpretor That's a pretty good innings! I have an old iPad about the same vintage. It can still run an old version of the app (just) but hasn't been able to load the website via browser for three or so years now. That stopped updating at v.12.7 though.
Have you checked what version browser you're running? If you've been using an older version of safari you could try downloading the latest compatible chrome and see if you have more luck with that…
0 -
I use firefox 135.0.1 on my 2019 Intel macbook pro and the website has been almost unusable the last week. It lags and affects my other tabs and the browser gives a message that I should close the page because its using excessive resources. I have cleared cache and cookies, tried troubleshoot mode, and I just reinstalled firefox but the issue persists. When I type in locations the standardized suggestion box is all the way and the bottom of the page. Today it is officially broken for me, I can't complete a search without it crashing my browser. Is anyone else experiencing this?
0 -
Probably slightly off the issue being raised here, but I have found that one time that I get the "Oops, something went wrong" message is when I accidentally keep an empty field checked for an "Exact" search. For example, omitting a first name and keeping the First Names box checked. As soon as I uncheck that field I get the results, as expected. I'm sure this did not happen in the past.
0 -
@Paul W Just an update on the exact search of an empty field. Engineering has agreed that the error message as it is now is a defect. Not sure if they will reset to the previous behavior or come up with a different way to alert the user that blank field exact searches are not supported.
1
