Public activity in user profile not shown #9574

New Issue

GiteaMirror · 2025-11-02T08:43:20-06:00

GiteaMirror commented

2025-11-02 08:43:20 -06:00

Originally created by @lafriks on GitHub (Sep 15, 2022).

Description

When server is private than when opening user profile it's public activity is shown only for admin users, for other users it's hidden

Gitea Version

1.17.2

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

Not relevant

Database

No response

Originally created by @lafriks on GitHub (Sep 15, 2022). ### Description When server is private than when opening user profile it's public activity is shown only for admin users, for other users it's hidden ### Gitea Version 1.17.2 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? Not relevant ### Database _No response_

GiteaMirror added the type/bug label 2025-11-02 08:43:20 -06:00

GiteaMirror commented

2025-11-02 08:43:21 -06:00

@lunny commented on GitHub (Sep 16, 2022):

Is the user public or private?

@lunny commented on GitHub (Sep 16, 2022): Is the user public or private?

GiteaMirror commented

2025-11-02 08:43:22 -06:00

@lafriks commented on GitHub (Sep 16, 2022):

As I could not replicate issue on my local instance, I tracked down issue to user table column keep_activity_private had null values instead of false. Still have no idea how they got there... could be either broken migration when column was added or ldap sync adding null values there 🤔

Anyway we should really make rule in database that all bool columns in database should be not null this would prevent such issues.

in case anyone else has this issue, temporary fix is to run this update in gitea database:

update "user" set keep_activity_private = false where keep_activity_private is null;

@lafriks commented on GitHub (Sep 16, 2022): As I could not replicate issue on my local instance, I tracked down issue to user table column `keep_activity_private` had null values instead of false. Still have no idea how they got there... could be either broken migration when column was added or ldap sync adding null values there 🤔 Anyway we should really make rule in database that all bool columns in database should be not null this would prevent such issues. in case anyone else has this issue, temporary fix is to run this update in gitea database: ```sql update "user" set keep_activity_private = false where keep_activity_private is null; ```

GiteaMirror commented

2025-11-02 08:43:22 -06:00

@KN4CK3R commented on GitHub (Sep 18, 2022):

@lafriks see #18871

@KN4CK3R commented on GitHub (Sep 18, 2022): @lafriks see #18871

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#9574