Broken links on dash page after renaming an organisation. #673

New Issue

GiteaMirror · 2025-11-02T03:32:37-06:00

GiteaMirror commented

2025-11-02 03:32:37 -06:00

Originally created by @dalito on GitHub (Apr 27, 2017).

Gitea version (or commit ref): release 1.10
Git version: 1.8.4
Operating system: Windows Server 2003
Database (use [x]):
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)

After renaming an organization the dash page contains links that still point to the old organization. All urls to the renamed repository should be either updated or removed upon renaming an organization.

I haven't tried yet if renaming a repository also produces broken links.

Originally created by @dalito on GitHub (Apr 27, 2017). - Gitea version (or commit ref): release 1.10 - Git version: 1.8.4 - Operating system: Windows Server 2003 - Database (use `[x]`): - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (provide example URL) After renaming an organization the dash page contains links that still point to the old organization. All urls to the renamed repository should be either updated or removed upon renaming an organization. I haven't tried yet if renaming a repository also produces broken links.

GiteaMirror added the type/bug label 2025-11-02 03:32:37 -06:00

GiteaMirror closed this issue

2025-11-02 03:32:37 -06:00

GiteaMirror commented

2025-11-02 03:32:38 -06:00

@ethantkoenig commented on GitHub (Jul 23, 2017):

@dalito I'm not able to reproduce. Can you confirm the issue is still present in latest version of gitea, and if so give more detailed intstructions on how to reproduce? Thanks.

@ethantkoenig commented on GitHub (Jul 23, 2017): @dalito I'm not able to reproduce. Can you confirm the issue is still present in latest version of gitea, and if so give more detailed intstructions on how to reproduce? Thanks.

GiteaMirror commented

2025-11-02 03:32:38 -06:00

@dalito commented on GitHub (Jul 26, 2017):

I can still reproduce this in Gitea Version 1.1.2:

Steps:

Create Organisation "Test-Orga"
Create a repository "repo1" in the Organisation
Commit to the repository

Now the dashboad shows an entry like "dalito pushed to master at Test-Orga/repo1"

Rename the Orgnaisation: "Test-Orga" -> "Test-Orga-renamed"
Go back to dashboad

The dashboad still shows the same entry: "dalito pushed to master at Test-Orga/repo1" (clicking the link gives a 404 error). Obviously, the dashboard is not correctly regenerated after the renaming.

@dalito commented on GitHub (Jul 26, 2017): I can still reproduce this in Gitea Version 1.1.2: Steps: 1. Create Organisation "Test-Orga" 2. Create a repository "repo1" in the Organisation 3. Commit to the repository Now the dashboad shows an entry like "dalito pushed to master at Test-Orga/repo1" 4. Rename the Orgnaisation: "Test-Orga" -> "Test-Orga-renamed" 5. Go back to dashboad The dashboad still shows the same entry: "dalito pushed to master at Test-Orga/repo1" (clicking the link gives a 404 error). Obviously, the dashboard is not correctly regenerated after the renaming.

GiteaMirror commented

2025-11-02 03:32:38 -06:00

@ethantkoenig commented on GitHub (Jul 28, 2017):

@dalito I followed your steps on master (fd45a032a7), and the name on the dashboard updated correctly. If you are able to reproduce this bug on master, please let me know, but otherwise it looks like this issue has already been fixed.

@ethantkoenig commented on GitHub (Jul 28, 2017): @dalito I followed your steps on master (fd45a032a7752e4da7e0388eb9661a7c32ff5c85), and the name on the dashboard updated correctly. If you are able to reproduce this bug on master, please let me know, but otherwise it looks like this issue has already been fixed.

GiteaMirror commented

2025-11-02 03:32:39 -06:00

@dalito commented on GitHub (Aug 22, 2017):

Unfortunately I cannot easily test with master but this issue is still present in the recent release 1.1.3. - When 1.2.0 comes out I will try again to confirm the fix.

@dalito commented on GitHub (Aug 22, 2017): Unfortunately I cannot easily test with master but this issue is still present in the recent release 1.1.3. - When 1.2.0 comes out I will try again to confirm the fix.

GiteaMirror commented

2025-11-02 03:32:39 -06:00

@lafriks commented on GitHub (Aug 22, 2017):

This is fixed in master so I'm closing it

@lafriks commented on GitHub (Aug 22, 2017): This is fixed in master so I'm closing it

GiteaMirror referenced this issue

2025-11-02 11:48:30 -06:00

[PR #673] [MERGED] Attach to release #15521

Sign in to join this conversation.