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

Proposal: hide explore menu #1475

Closed
yusefmaali opened this issue Apr 9, 2017 · 11 comments
Closed

Proposal: hide explore menu #1475

yusefmaali opened this issue Apr 9, 2017 · 11 comments
Labels
issue/stale type/feature Completely new functionality. Can only be merged if feature freeze is not active.

Comments

@yusefmaali
Copy link

In some situations, the explore page may not be needed.

It should be very useful to have a config settings to hide at all the explore menu entry.
Something very similar to (for example) "DISABLE_REGISTRATION", we may have a "DISABLE_EXPLORE_MENU".

Thank you!

@lunny lunny added the type/feature Completely new functionality. Can only be merged if feature freeze is not active. label Apr 9, 2017
@lunny lunny added this to the 1.x.x milestone Apr 9, 2017
@strk
Copy link
Member

strk commented Apr 9, 2017 via email

@yusefmaali
Copy link
Author

yusefmaali commented Apr 10, 2017

This sounds pretty interesting.
Can you give some hints to look for more details?

@strk
Copy link
Member

strk commented Apr 10, 2017 via email

@yusefmaali
Copy link
Author

sure!

I need to pass through a Golang tutorial, then I will contribute for sure!

@strk
Copy link
Member

strk commented Apr 10, 2017 via email

@yusefmaali
Copy link
Author

yusefmaali commented Apr 10, 2017

Of course, you're right. I thought I needed to run gitea from its sources. I'm seeing the compiled version is enough.

@Spenhouet
Copy link

This would be a needed feature. User case: Non admin users should not be able to see other users and other repositories. Not sure, but hiding the explore page (also sub pages) could solve that.

@lafriks
Copy link
Member

lafriks commented Oct 3, 2018

@Spenhouet just hiding menu won't solve that. Access should be controlled also when opening repository page and for that there is private repository setting. If it is set other users won't be able to see that repository

@stale
Copy link

stale bot commented Jan 7, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label Jan 7, 2019
@stale
Copy link

stale bot commented Feb 22, 2019

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale stale bot closed this as completed Feb 22, 2019
@lafriks lafriks removed this from the 1.x.x milestone Feb 26, 2019
@lesderid
Copy link

Was this added? Seems like a sensible feature to have.

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/stale type/feature Completely new functionality. Can only be merged if feature freeze is not active.
Projects
None yet
Development

No branches or pull requests

6 participants