Skip to content
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

Users in Team with Administrator permissions get 404 when accessing repository #4713

Closed
2 of 7 tasks
weirdbiz opened this issue Aug 15, 2018 · 6 comments · Fixed by #4719
Closed
2 of 7 tasks

Users in Team with Administrator permissions get 404 when accessing repository #4713

weirdbiz opened this issue Aug 15, 2018 · 6 comments · Fixed by #4719
Labels

Comments

@weirdbiz
Copy link

weirdbiz commented Aug 15, 2018

Gitea version (or commit ref): 1.5.0

  • Git version: 2.18.0-windows.1
  • Operating system: Windows 7 Professional
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes
    • No
    • Not relevant
  • Log gist:

Description

Issue: Users in Team with Administrator permissions get 404 when accessing private repository.

Steps to reproduce:

  1. User1 creates: Organization, Private Repository inside it, Team with Administrative permissions to that Repository.
  2. User1 adds User2 to the Team created before.
  3. User2 opens link to the Repository and gets 404.

Bug is reproducible only with Teams that have Administrator permissions. Teams with Read or Write permissions work fine.

@lunny
Copy link
Member

lunny commented Aug 15, 2018

Please give the link you reproduce that on try.gitea.io

@adelowo
Copy link
Member

adelowo commented Aug 15, 2018

Would try to replicate this in a bit

@weirdbiz
Copy link
Author

Sorry, forgot important thing: Repository should be Private.

@adelowo
Copy link
Member

adelowo commented Aug 15, 2018

Can confirm bug exists.... Would look at sending a fix before the day runs out

@rvillablanca
Copy link
Contributor

rvillablanca commented Aug 21, 2018

when is possible get this fix ? I mean, are you planning make a minor release for this ?

@adelowo
Copy link
Member

adelowo commented Aug 21, 2018

It will be backported to 1.5

I’ve sent a PR already ( #4719 ) and it requires approval from one more maintainer

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants