1.16.9+: Cannot edit issues / PRs unless admin #9369

New Issue

GiteaMirror · 2025-11-02T08:36:43-06:00

GiteaMirror commented

2025-11-02 08:36:43 -06:00

Originally created by @PaulFocus on GitHub (Aug 8, 2022).

Description

The problem started to appear after upgrade from 1.15.11 to 1.16.9+:

While the admin user is able to edit PR comments or issue comment, no other user is not. If a normal user wants to edit the comment (even if it has been created by him), the button just changes from light-green to dark-green, but the comment is not saved.

Before clicking the Save =("Speichern") button of a PR:

After clicking the button:

Expected behaviour: The user is able to edit and save the comment.
Current behaviour: The user is not able to do so.

All repositories are private. A default team dev-focus has access to the repositories with the admin user always being the owner. All the other users being members in that team. (Screenshots on white background are created as admin user, all other are created as "member" user.)

gitea doctor shows no problems.

It seems there has been some change from 1.15.x to 1.16.x which I am missing.

Best regards,
Paul

Gitea Version

1.16.9+2-g9aa13c585

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

2.20.1 (git --version)

Operating System

Linux Raspbian Buster

How are you running Gitea?

database: MariaDB
running on Raspberry Pi 4

Database

MySQL

Originally created by @PaulFocus on GitHub (Aug 8, 2022). ### Description The problem started to appear after upgrade from 1.15.11 to 1.16.9+: While the admin user is able to edit PR comments or issue comment, no other user is not. If a normal user wants to edit the comment (even if it has been created by him), the button just changes from light-green to dark-green, but the comment is not saved. Before clicking the `Save` =("Speichern") button of a PR: ![gitea_cannotedit1](https://user-images.githubusercontent.com/49278956/183404173-e9d5bb57-000c-4b11-8e1e-1bb45f07e45c.png) After clicking the button: ![gitea_cannotedit2](https://user-images.githubusercontent.com/49278956/183404180-fd030628-509a-4f93-b96f-c4e14f7adfb1.png) Expected behaviour: The user is able to edit and save the comment. Current behaviour: The user is not able to do so. All repositories are private. A default team **dev-focus** has access to the repositories with the admin user always being the **owner**. All the other users being **members** in that team. (Screenshots on white background are created as admin user, all other are created as "member" user.) ![gitea_team](https://user-images.githubusercontent.com/49278956/183403855-86d6b970-c763-4bbd-9e34-87fcb97a23d7.png) ![gitea_accessmatrix](https://user-images.githubusercontent.com/49278956/183403977-f9693521-f631-4416-8d93-3ebd2188dc2a.png) `gitea doctor` shows no problems. It seems there has been some change from 1.15.x to 1.16.x which I am missing. Best regards, Paul ### Gitea Version 1.16.9+2-g9aa13c585 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version 2.20.1 (git --version) ### Operating System Linux Raspbian Buster ### How are you running Gitea? database: MariaDB running on Raspberry Pi 4 ### Database MySQL

GiteaMirror added the type/bug label 2025-11-02 08:36:43 -06:00

GiteaMirror closed this issue

2025-11-02 08:36:44 -06:00

GiteaMirror commented

2025-11-02 08:36:44 -06:00

@PaulFocus commented on GitHub (Aug 22, 2022):

Seems to have been some browser cache-related issue, works now on all machines.

@PaulFocus commented on GitHub (Aug 22, 2022): Seems to have been some browser cache-related issue, works now on all machines.

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#9369