Home button should be hidden when LANDING_PAGE is set to "explore" or "organizations" #2159

New Issue

GiteaMirror · 2025-11-02T04:25:38-06:00

GiteaMirror commented

2025-11-02 04:25:38 -06:00

Originally created by @0rzech on GitHub (Aug 8, 2018).

Gitea version (or commit ref): 1.4.3
Git version: Not relevant
Operating system: Not relevant
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
- Not relevant
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
Log gist: Not relevant

Description

When app.ini contains LANDING_PAGE = explore, all of the three buttons (the cup, Home and Explore) point to the same place. This is redundant and kind of confusing. See here for an example.

So what would I expect? When LANDING_PAGE is set to home, both home and explore buttons should be visible, as they point to different locations. When LANDING_PAGE is set to explore or organizations, the home button should be hidden and explore button should just be labelled home, as it is it's real role now.

Originally created by @0rzech on GitHub (Aug 8, 2018). - Gitea version (or commit ref): 1.4.3 - Git version: Not relevant - Operating system: Not relevant - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - [x] Not relevant - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - [ ] Not relevant - Log gist: Not relevant ## Description When `app.ini` contains `LANDING_PAGE = explore`, all of the three buttons (the cup, `Home` and `Explore`) point to the same place. This is redundant and kind of confusing. See [here](https://orzechowski.tech/git) for an example. So what would I expect? When `LANDING_PAGE` is set to `home`, both home and explore buttons should be visible, as they point to different locations. When `LANDING_PAGE` is set to `explore` or `organizations`, the home button should be hidden and explore button should just be labelled `home`, as it is it's real role now.

GiteaMirror added the topic/ui label 2025-11-02 04:25:38 -06:00

GiteaMirror closed this issue

2025-11-02 04:25:38 -06:00

GiteaMirror commented

2025-11-02 04:25:39 -06:00

@techknowlogick commented on GitHub (Aug 9, 2018):

Perhaps instead of renaming explore to home, just remove the home link when the above situation occurs.

@techknowlogick commented on GitHub (Aug 9, 2018): Perhaps instead of renaming explore to home, just remove the home link when the above situation occurs.

GiteaMirror commented

2025-11-02 04:25:39 -06:00

@0rzech commented on GitHub (Aug 9, 2018):

@techknowlogick The home button is removed in above situation. Explore is just additionally renamed to home, because this is exactly what explore button means when LANDING_PAGE is explore or organizations. Also, this will be consistent for people visiting different instances of Gitea. Home-labelled button will always be there for them, just defaulting to different pages. Of course, if you still want me not to rename explore in addition to hiding home, just let me know and I will update PR.

@0rzech commented on GitHub (Aug 9, 2018): @techknowlogick The home button is removed in above situation. Explore is just additionally renamed to home, because this is exactly what explore button means when `LANDING_PAGE` is `explore` or `organizations`. Also, this will be consistent for people visiting different instances of Gitea. Home-labelled button will always be there for them, just defaulting to different pages. Of course, if you still want me not to rename explore in addition to hiding home, just let me know and I will update PR.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#2159