404 page after transferring repo ownership #4451

New Issue

GiteaMirror · 2025-11-02T05:51:13-06:00

GiteaMirror commented

2025-11-02 05:51:13 -06:00

Originally created by @guillep2k on GitHub (Dec 6, 2019).

Gitea version (or commit ref): 1.10.0

Description

If a plain user from an organization transfers a private repository to the organization, the operation succeeds but the user gets redirected to a page to which they no longer have permissions (e.g. the user does not belong to the owners team) and a 404 is rendered.

This may also happen with other kinds of transfer ownership (e.g. user to user).

I think it's important for the user to know whether the operation was successful, so they should be redirected to their own home with a success message.

Originally created by @guillep2k on GitHub (Dec 6, 2019). - Gitea version (or commit ref): 1.10.0 ## Description If a plain user from an organization transfers a private repository to the organization, the operation succeeds but the user gets redirected to a page to which they no longer have permissions (e.g. the user does not belong to the owners team) and a 404 is rendered. This may also happen with other kinds of transfer ownership (e.g. user to user). I think it's important for the user to know whether the operation was successful, so they should be redirected to their own home with a success message.

GiteaMirror added the issue/confirmed type/bug labels 2025-11-02 05:51:13 -06:00

GiteaMirror closed this issue

2025-11-02 05:51:13 -06:00

GiteaMirror commented

2025-11-02 05:51:14 -06:00

@lunny commented on GitHub (Dec 6, 2019):

So the redirect address was wrong after transfer succeed.

@lunny commented on GitHub (Dec 6, 2019): So the redirect address was wrong after transfer succeed.

GiteaMirror commented

2025-11-02 05:51:14 -06:00

@guillep2k commented on GitHub (Dec 6, 2019):

The user was redirected to the same page (repo settings), but the user no longer had permission to access that. I don't have that problem being admin or owner; only plain users get this error.

@guillep2k commented on GitHub (Dec 6, 2019): The user was redirected to the same page (repo settings), but the user no longer had permission to access that. I don't have that problem being admin or owner; only plain users get this error.

GiteaMirror commented

2025-11-02 05:51:15 -06:00

@stale[bot] commented on GitHub (Feb 4, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 4, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 05:51:15 -06:00

@lunny commented on GitHub (Apr 28, 2023):

I think this could be closed because now every transfer need to be confirmed by receivers.

@lunny commented on GitHub (Apr 28, 2023): I think this could be closed because now every transfer need to be confirmed by receivers.

GiteaMirror referenced this issue

2025-11-02 13:09:39 -06:00

[PR #4495] [MERGED] Fix migration from older releases #17398

Sign in to join this conversation.