You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: woodpeck [Submitted to the original trac issue database at 3.39pm, Sunday, 8th February 2009]
I have more than one OSM account and I am currently logged in with account #1. Account #2 receives a message and an e-mail is sent with a link that says "you can reply at .../message/reply/1234". Clicking this link leads to an empty browser window - likely some kind of Ruby exception behind the scenes because the logged-in user and the message owner are not the same.
The desired behaviour would be to show a message saying "you are logged in as X and you cannot read this message, click here to re-login" or so. (Automatically kicking the user out would perhaps be undesirable.)
The text was updated successfully, but these errors were encountered:
Author: tomhughes [Added to the original trac issue at 3.13pm, Sunday, 28th February 2010]
(In [20207]) Tidy up error handling in the message controller, and make it redirect to
the login page if you are logged in as the wrong user. Closes #1569.
Reporter: woodpeck
[Submitted to the original trac issue database at 3.39pm, Sunday, 8th February 2009]
I have more than one OSM account and I am currently logged in with account #1. Account #2 receives a message and an e-mail is sent with a link that says "you can reply at .../message/reply/1234". Clicking this link leads to an empty browser window - likely some kind of Ruby exception behind the scenes because the logged-in user and the message owner are not the same.
The desired behaviour would be to show a message saying "you are logged in as X and you cannot read this message, click here to re-login" or so. (Automatically kicking the user out would perhaps be undesirable.)
The text was updated successfully, but these errors were encountered: