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

Some buttons doesn't work on issues screen #19245

Closed
maherma-adg opened this issue Mar 28, 2022 · 7 comments
Closed

Some buttons doesn't work on issues screen #19245

maherma-adg opened this issue Mar 28, 2022 · 7 comments
Labels

Comments

@maherma-adg
Copy link

Description

After update from 1.15.9 to 1.16.1 the close issue button stop working, when you hit the button nothing happens.
Checking screen I detect some buttons stop working too:

  • Add time
  • Start timer
  • Edit issue title

Other buttons still works:

  • New Issue
  • Comment
  • Tags
  • Milestone

I update gitea to 1.17.0+dev-351-g54961f3ac but get the same result.

Gitea Version

1.16.1 and up

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

2.25.1

Operating System

linux

How are you running Gitea?

Gitea server is downloaded from gitea repo.
Gitea is running as systemd service.
server is ubuntu 20.20.4

Database

SQLite

@maherma-adg maherma-adg changed the title Some button doesn't work on issues screen Some buttons doesn't work on issues screen Mar 28, 2022
@maherma-adg
Copy link
Author

More info: Tested on Firefox and Chrome do the same result.

@silverwind
Copy link
Member

Any JS errors visible in the browser console/devtools?

@maherma-adg
Copy link
Author

Browsers show this message when reload page:

jQuery.Deferred exception: Cannot read properties of undefined (reading 'adminUserListSearchForm') TypeError: Cannot read properties of undefined (reading 'adminUserListSearchForm')

but no reactions when click on buttons

@wxiaoguang
Copy link
Contributor

Remove your customized templates.

@maherma-adg
Copy link
Author

Solved. Now I'll try to restore mermaid and katex render to pages.
Thanks for the solution.

@wxiaoguang
Copy link
Contributor

@silverwind how about show JS errors to end users, like this one #18971

There should be no JS error during normal usage. If there is an error, it must be reported and fixed.

@silverwind
Copy link
Member

Yeah, sounds like a good idea.

@go-gitea go-gitea locked and limited conversation to collaborators Apr 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants