#7783 After typing a bug comment, it is lost with redirect to "You are already logged in"


I just tried typing in a comment on a bug. When I clicked post, it popped up a page saying "You are already logged in." And everything I typed for the comment was lost. Not happy!

I had had my browser open overnight. I had opened a saved link directly to that bug page.


  • Anonymous - 2014-06-02
    • status: unread --> pending
    • assigned_to: Chris Tsai
  • Anonymous - 2014-06-02


    It sounds like you may have hit an anti-spam filter due to the fact that the window was opened at a drastically different time from when the post was attempted.

    That said, I highly recommend the "Lazarus" browser plugin, I have personally found it invaluable for retrieving lost text from bad form submissions, whether on this site or elsewhere: http://getlazarus.com/

    Chris Tsai, SourceForge.net Support

  • Tony Houghton

    Tony Houghton - 2014-06-18

    I've been experiencing similar problems. Additionally, I just tried to post a comment to a discussion thread for roxterm. I had only recently opened the browser tab, but it showed I was already logged in. But whenI posted the comment it took me to the login page. Login was successful, but it just took me to the welcome page and my comment was lost when I went back. I tried again to post a comment and this time it was successful.

    I don't think it's caused by the window being opened too long before posting the comment. It could be caused by logging in to the same account from more than one PC/browser. But SF should be able to make up its mind whether I'm logged in or not, and definitely not lose text I've entered if I have to log in between writing a comment and posting it.

  • Anonymous - 2014-07-01
    • status: pending --> self-service
  • Anonymous - 2014-07-01

    Another related issue is with the way we handle login requests currently. In particular, with how logins are handled across codebases on our site. We are however planning on a full rewrite of our login/authentication system. This issue should go away once this is complete. If you're still having problems once this rewrite is complete (I expect there to be a visual change on the login page), let us know.

    In the meantime, the best way to workaround this is to first visit the login page (whether it says you're logged in or not) before attempting further authenticated action.

    Chris Tsai, SourceForge.net Support


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks