-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Explore repositories at try.gitea.io #945
Comments
I tried to reproduce it, but it worked fine for me. I was logged in at the time. After reading the models.User i logged out and tried it again, then this error appeared. So i think you try to show something only the logged in user has and this is why it fails. |
Yes, that might very well be the problem. But this is try.gitea.io, where people go to test your software - should it really be a requirement to create a user for that? For comparison https://try.gogs.io/explore/repos works fine without a user. If you want to require a user you should clearly write some message about this so that a new user knows what to do. Another approach might be to create a demo user for people to use. |
I am totally with you on this one. I also think it should work without an account for public projects. All i wanted was to add some more info to the issue as it could help find the problem faster. Sorry if that was not clear enough. |
@ea2973929 Unfortunately #940 introduced this bug, @appleboy could you take a look at this? |
Yep, confirmed that |
same for me on my installation. |
@ea2973929 @arkraft @xsteadfastx please confirm this has been fixed via #946 |
Works for me. I'm not sure what process you have around this. Should I close it as the creator of the issue? |
Please close this. |
Description
How to reproduce
Expected
2. Some sort of demo page of gitea with repositories
Actual
2. Text error message: template: explore/repo_list:5:200: executing "explore/repo_list" at <.Owner.Name>: can't evaluate field Name in type *models.User
Extra comment: "Because first impressions last"
The text was updated successfully, but these errors were encountered: