Skip to content
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

Feed and watchlist: 500 internal error #389

Closed
cascafico opened this issue Sep 16, 2019 · 8 comments · Fixed by OSMCha/osmcha-django#314
Closed

Feed and watchlist: 500 internal error #389

cascafico opened this issue Sep 16, 2019 · 8 comments · Fixed by OSMCha/osmcha-django#314

Comments

@cascafico
Copy link

I want to track some OSM vandalism, relying on a compiled OSMCHA watchlist.

Saved filter RSS links work fine (ie: bbox, polygon AOI etc). I successfully tested them on a couple of Telegram feed readers. But whenever I set "Watchlisted users to "yes", save the updated filter and update telegram bots RSS link, such link is not funcional anymore, yelding something like "(500) internal server error".

All above operations are done on Chromium (v.60.0.31112.89) and Chrome (v.73.0.3683.75)

@willemarcel
Copy link
Collaborator

@cascafico thank you for your report. I'll analyse this error this week.

@camelCaseNick
Copy link

I have the same problem with getting a 500 Internal Server Error. It also occurs when trusted mapped are hidden, but not, when verified mapping teams are.

@BalooUriza
Copy link

At this point, the feeds don't work at all, with feed URLs providing the same thing as the normal web interface.

@camelCaseNick
Copy link

@BalooUriza If you have a filter list with watchlisted users or trusted mappers settings, you get a 500, but under that circumstances you always get redirected to /, so that you see the normal web interface. (look into the inspector if you don't trust me)

@BalooUriza
Copy link

Is it possible to get that corrected when such filters are in place??

@momu
Copy link

momu commented Apr 27, 2020

@willemarcel thanks for fixing it, when will the fix be available on https://osmcha.org?

@willemarcel
Copy link
Collaborator

@momu we'll update it today yet I think.

@willemarcel
Copy link
Collaborator

@momu osmcha.org is updated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants