-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If repo.projects unit is disabled, it's still shown in user profile page #25934
Comments
When Lines 833 to 864 in 24b49bc
|
lunny
pushed a commit
that referenced
this issue
Jul 29, 2023
Fix #25934 Add `ignoreGlobal` parameter to `reqUnitAccess` and only check global disabled units when `ignoreGlobal` is true. So the org-level projects and user-level projects won't be affected by global disabled `repo.projects` unit.
GiteaBot
pushed a commit
to GiteaBot/gitea
that referenced
this issue
Jul 29, 2023
Fix go-gitea#25934 Add `ignoreGlobal` parameter to `reqUnitAccess` and only check global disabled units when `ignoreGlobal` is true. So the org-level projects and user-level projects won't be affected by global disabled `repo.projects` unit.
silverwind
pushed a commit
that referenced
this issue
Jul 29, 2023
Backport #26182 by @Zettat123 Fix #25934 Add `ignoreGlobal` parameter to `reqUnitAccess` and only check global disabled units when `ignoreGlobal` is true. So the org-level projects and user-level projects won't be affected by global disabled `repo.projects` unit. Co-authored-by: Zettat123 <zettat123@gmail.com>
project-mirrors-bot-tu bot
pushed a commit
to project-mirrors/forgejo-as-gitea-fork
that referenced
this issue
Jan 23, 2025
Backport go-gitea#26182 by @Zettat123 Fix go-gitea#25934 Add `ignoreGlobal` parameter to `reqUnitAccess` and only check global disabled units when `ignoreGlobal` is true. So the org-level projects and user-level projects won't be affected by global disabled `repo.projects` unit. Co-authored-by: Zettat123 <zettat123@gmail.com> (cherry picked from commit 3a29712)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
I'm using the DISABLE_REPO_UNITS to disable the projects unit. In most places, the project links are removed but in the user profile, the link still exists.
Clicking on that, leads to a 404 page
Screenshots
Gitea Version
1.20
Can you reproduce the bug on the Gitea demo site?
No
Operating System
Docker on Debian
Browser Version
Chrome 114
The text was updated successfully, but these errors were encountered: