Deactivate account #836

New Issue

GiteaMirror · 2025-11-02T03:38:16-06:00

GiteaMirror commented

2025-11-02 03:38:16 -06:00

Originally created by @lcges on GitHub (Jun 22, 2017).

Gitea version (or commit ref): 1.1.0
Git version: last version
Operating system: FreeBSD 11
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant

There is a bug when I deactivate account emails with all work progress are sending still to email from deactivated account. When account is deactivated it must be deactivated totally, all functions of account should be deactivated when account will be deactivated.

...

If this issue involves the Web Interface, please include a screenshot

Originally created by @lcges on GitHub (Jun 22, 2017). - Gitea version (or commit ref): 1.1.0 - Git version: last version - Operating system: FreeBSD 11 - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant There is a bug when I deactivate account emails with all work progress are sending still to email from deactivated account. When account is deactivated it must be deactivated totally, all functions of account should be deactivated when account will be deactivated. ... ![2017-06-22t12 02 59 02 00-831x39](https://user-images.githubusercontent.com/19255071/27428672-17902fd2-5743-11e7-95d6-88d1f22c291f.png) **If this issue involves the Web Interface, please include a screenshot**

GiteaMirror added the type/bug label 2025-11-02 03:38:16 -06:00

GiteaMirror closed this issue

2025-11-02 03:38:16 -06:00

GiteaMirror commented

2025-11-02 03:38:17 -06:00

@daviian commented on GitHub (Aug 20, 2017):

@lunny You can assign me to this issue

@daviian commented on GitHub (Aug 20, 2017): @lunny You can assign me to this issue

GiteaMirror commented

2025-11-02 03:38:17 -06:00

@lafriks commented on GitHub (Aug 20, 2017):

@daviian only members can be assigned to issue but work freely on it

@lafriks commented on GitHub (Aug 20, 2017): @daviian only members can be assigned to issue but work freely on it

GiteaMirror commented

2025-11-02 03:38:17 -06:00

@daviian commented on GitHub (Aug 21, 2017):

Currently there are two flags describing the active state of a user.
The is_active and prohibited_login flags. Imo a user is inactive if one of both is set.
Please correct me if I am wrong.

@daviian commented on GitHub (Aug 21, 2017): Currently there are two flags describing the active state of a user. The `is_active` and `prohibited_login` flags. Imo a user is **inactive** if one of both is set. Please correct me if I am wrong.

GiteaMirror commented

2025-11-02 03:38:17 -06:00

@lunny commented on GitHub (Aug 22, 2017):

Just found some different between the two flags.
is_active is false, you and your public repos will not be visited by others.
prohibited_login is false, you and your public repos will still be visited by others

@lunny commented on GitHub (Aug 22, 2017): Just found some different between the two flags. `is_active` is false, you and your public repos will not be visited by others. `prohibited_login` is false, you and your public repos will still be visited by others

GiteaMirror commented

2025-11-02 03:38:18 -06:00

@lafriks commented on GitHub (Aug 22, 2017):

But user should not get notifications in both cases I think

@lafriks commented on GitHub (Aug 22, 2017): But user should not get notifications in both cases I think

GiteaMirror commented

2025-11-02 03:38:18 -06:00

@lunny commented on GitHub (Aug 22, 2017):

@lafriks I agree with that.

@lunny commented on GitHub (Aug 22, 2017): @lafriks I agree with that.

GiteaMirror commented

2025-11-02 03:38:18 -06:00