Skip to content

500 Server Error after login if User has no allowed visibility mode #23211

Closed
@cchartmann

Description

@cchartmann

Description

  1. set your user to public visible
  2. set ALLOWED_USER_VISIBILITY_MODES = limited,private in app.ini
  3. log in
  4. enjoy the big 500 that you now can see
  5. click on something and you will see, that you are successful logged in

I would expect to see some message, that tells the user, that his visibility is not allowed or something else more useful than an Internal Server Error, so he knows, he can change his visibility to avoid this error the next time.
The Admin will see the error and the reason for it the next time he checks the logs.

It would also make sense to add the information to the documentation of app.ini, so if someone makes a change on ALLOWED_USER_VISIBILITY_MODES, he knows about that.

Gitea Version

1.18.5

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

Cent OS 7

How are you running Gitea?

i use an release from Github on Uberspace
see this Guide for more info:
https://lab.uberspace.de/guide_gitea/

Database

MySQL

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions