-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Place search is broken #9822
Comments
Confirming that I also get a 404 for the request to https://nominatim.openstreetmap.org/search/ and that only POIs/data loaded in the current view display in search, in agreement with what Ben noted. |
This is caused by osm-search/Nominatim#3134, although I thought openstreetmap/operations#920 would have temporarily fixed the issue... |
@k-yle I still get the CORS error. Is this maybe something different from the other "search/" issues? |
I see this was fixed by @tyrasd last week via a454aa3 and a460013. @tyrasd since the change referenced in #9822 (comment) does not solve the issue on production, maybe this is something for a hotfix release? I will close the issue now, since it is handled pending deployment… |
URL
No response
How to reproduce the issue?
It looks like the same issue Ben describes in facebook/Rapid#1007 applies to iD as well. I get a CORS error when searching for Huston.
Screenshot(s) or anything else?
No response
Which deployed environments do you see the issue in?
Released version at openstreetmap.org/edit
What version numbers does this issue effect?
No response
Which browsers are you seeing this problem on?
No response
The text was updated successfully, but these errors were encountered: