Logged out while editing #5512

New Issue

GiteaMirror · 2025-11-02T06:27:13-06:00

GiteaMirror commented

2025-11-02 06:27:13 -06:00

Originally created by @rixx on GitHub (Jun 7, 2020).

If you edit an issue and keep it open in a tab for some time, your session may end. But if you click "save", there is no indication of an error at all, despite your changes not being saved! Only upon reloading the page you will be redirected to the login screen, with all your changes being irrecoverably lost. Especially with larger edits, this is quite frustrating.

I understand that mitigating this completely is complex (eg maintaining an edit log/drafts in the browser's localStorage would be a way), but the least gitea could do would be a show of an error message instead of pretending that changes have been saved correctly.

Gitea version (or commit ref): 1.11.4

Originally created by @rixx on GitHub (Jun 7, 2020). If you edit an issue and keep it open in a tab for some time, your session may end. But if you click "save", there is no indication of an error at all, despite your changes not being saved! Only upon reloading the page you will be redirected to the login screen, with all your changes being irrecoverably lost. Especially with larger edits, this is quite frustrating. I understand that mitigating this completely is complex (eg maintaining an edit log/drafts in the browser's localStorage would be a way), but the least gitea could do would be a show of an error message instead of pretending that changes have been saved correctly. - Gitea version (or commit ref): 1.11.4

GiteaMirror added the issue/needs-feedback type/bug labels 2025-11-02 06:27:13 -06:00

GiteaMirror closed this issue

2025-11-02 06:27:14 -06:00

GiteaMirror commented

2025-11-02 06:27:15 -06:00

@stale[bot] commented on GitHub (Aug 6, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Aug 6, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 06:27:15 -06:00

@rixx commented on GitHub (Aug 6, 2020):

bump

@rixx commented on GitHub (Aug 6, 2020): bump

GiteaMirror commented

2025-11-02 06:27:15 -06:00

@stale[bot] commented on GitHub (Oct 12, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Oct 12, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 06:27:15 -06:00

@zeripath commented on GitHub (Oct 12, 2020):

Does this really still happen with the notification event stream?

@zeripath commented on GitHub (Oct 12, 2020): Does this really still happen with the notification event stream?

GiteaMirror commented

2025-11-02 06:27:15 -06:00

@wxiaoguang commented on GitHub (Dec 8, 2021):

Duplicate of