Skip to content

Gitea 1.14.0 - Configuration page - SSH Configuration - Use Built-In Server value is reversed #15461

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

Closed
1 of 6 tasks
GeyserLaPunk opened this issue Apr 13, 2021 · 1 comment · Fixed by #15464
Closed
1 of 6 tasks
Labels
good first issue Likely to be an easy fix topic/ui Change the appearance of the Gitea UI type/bug
Milestone

Comments

@GeyserLaPunk
Copy link

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

Description

...
Configuration page SSH Configuration Use Built-In Server check mark is reversed.
I have START_SSH_SERVER = true in app.ini but on the page I'm getting an "X".
If I change it to false and restart, I then get a check mark.

It was working correctly in 1.13.7 and 1.13.6.

Screenshots

@techknowlogick
Copy link
Member

For anyone looking at a PR for this, I suspect the change required would need to be here: https://github.com/go-gitea/gitea/blob/master/templates/admin/config.tmpl#L64-L97

@techknowlogick techknowlogick added good first issue Likely to be an easy fix type/bug topic/ui Change the appearance of the Gitea UI labels Apr 14, 2021
@lunny lunny added this to the 1.14.1 milestone Apr 14, 2021
@go-gitea go-gitea locked and limited conversation to collaborators Jun 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
good first issue Likely to be an easy fix topic/ui Change the appearance of the Gitea UI type/bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants