cannot access account settings #487
Comments
Author: tom[at]compton.nu What browser are you using? Only when I try it on my local test setup I find that Firefox tries to go to a URL with a UTF-8 encoded version of the character instead of an ISO-8859-1 encoded one. In other words this URL: http://www.openstreetmap.org/user/Marc+Sch%C3%BCtz/account That URL works for me on my test setup - does it work for you on the live site? |
Author: schuetzm[at]gmx.net I'm using Firefox. The UTF8 encoded URL you give does indeed work, however I cannot save my settings, because the form has action="/user/Marc+Sch%FCtz/account". So this is probably not a client-side problem. The page itself is served with a charset of UTF-8 (according to Firefox's "page information"). |
Author: tom[at]compton.nu I've just tried this and I still can't recreate it I'm afraid - the form seems to have the correct UTF-8 URL and submitting it works fine... Is this still going wrong for you? |
Author: schuetzm[at]gmx.net Yes; the only difference now is that I don't even get an error message anymore, only a completely empty page. |
Author: tom[at]compton.nu OK. I think I've solved this - your display name was actually in the database in iso-8859-1 rather than UTF-8. Presumably because it was set before the database was converted. I couldn't reproduce it locally because when I created a new user it was being created with the name stored as UTF-8.... I've changed your database record to be in UTF-8 now so hopefully everything should work. |
Author: schuetzm[at]gmx.net That fixes it, thanks! |
Reporter: schuetzm[at]gmx.net
[Submitted to the original trac issue database at 10.49pm, Friday, 25th May 2007]
Whenever I try to access my account settings at http://www.openstreetmap.org/user/Marc+Sch%FCtz/account, I get the following error:
Application error
Change this error message for exceptions thrown outside of an action (like in Dispatcher setups or broken Ruby code) in public/500.html
Maybe this is related to the %FC in the URL?
The text was updated successfully, but these errors were encountered: