Prevent edits when the user has been logged out #2113
Comments
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
|
A feature request that hasn't been responded to isn't stale.... |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
|
@o1egl sorry for the ping but I don't know how to prevent this FR from being auto-closed. I understand if it's not a priority but IMO FRs shouldn't be auto-closed just because of inactivity. |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
|
. |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
|
. |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
|
. |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
|
. |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
|
@o1egl looking at the list of closed issues it seems like many are being closed as stale, including both feature requests and clear bugs like #2334. Is this stale closure behavior really working as intended? |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
|
. |
|
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
|
. |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
|
🙄 |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
|
. |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
|
. |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
|
I give up, clearly this repo is abandoned. |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
|
This issue was closed because it has been stalled for 5 days with no activity. |
Is your feature request related to a problem? Please describe.
Several times now I've made a number of edits to a file, only to hit save and be redirected to the login page because the window had been open too long. This makes it very easy to lose work and as best I can tell there's no indication on the page that you've been logged out until you try to save.
Describe the solution you'd like
It would be helpful if the page prevented edits and made it clear the user has been logged out. For example by proactively redirecting to the login page, changing the text box to read-only, or displaying a login overlay over the file so the user can log in again without losing their work.
Describe alternatives you've considered
More a separate FR than an alternative, but initially I was looking for a setting to configure the logout duration. It seems like it's quite short, a few hours or less, but I didn't find a setting to customize this duration.
Additional context
N/A
The text was updated successfully, but these errors were encountered: