feat(profile): add configurable profile visibility with access control #39
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: McPringle/fitpub#39
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "McPringle/feat/public-profiles"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This change adds configurable profile visibility settings: public, followers only, or private. Access to profile pages and profile-related data is now enforced centrally, and the UI handles restricted profiles with a clear message.
Previously, anonymous users who clicked on a user profile were redirected to the login page. In addition, users editing their own profile had no clear indication of who could actually see it. The new visibility setting makes that behavior explicit and understandable, while putting control over profile visibility directly in the hands of the user. The default is followers only, since that most closely matches the behavior that was effectively observed before.
For example, I would like to make my own profile publicly visible so it can be accessed directly without ambiguity: sattelgeschichten.ch/users/McPringle
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.