Show everything wrong with app.ini #14231

Open
opened 2025-11-02 11:07:06 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @theAkito on GitHub (Mar 8, 2025).

Description

When checking out configuration Summary via Site Administration Web UI, there is a header, saying that something like, for example, LFS_CONTENT_PATH is deprecated and then 2 more, as in 2 more issues...

This gets even weirder, when having these configuration issues and, for example, sending a test mail and you cannot see the result, because it will continue to only show, that LFS_CONTENT_PATH is deprecated and then 2 more.....

The Web UI should show all bad configuration options and even when the configuration is not fully correct, the test mail result should also be displayed in the header area.

Screenshots

Image

Gitea Version

1.23.5

Can you reproduce the bug on the Gitea demo site?

No

Operating System

No response

Browser Version

FireFox

Originally created by @theAkito on GitHub (Mar 8, 2025). ### Description When checking out configuration Summary via `Site Administration` Web UI, there is a header, saying that something like, for example, `LFS_CONTENT_PATH` is deprecated and then `2 more`, as in 2 more issues... This gets even weirder, when having these configuration issues and, for example, sending a test mail and you cannot see the result, because it will continue to only show, that `LFS_CONTENT_PATH` is deprecated and then `2 more`..... The Web UI should show all bad configuration options and even when the configuration is not fully correct, the test mail result should also be displayed in the header area. ### Screenshots ![Image](https://github.com/user-attachments/assets/89d40e61-ac64-49a0-ada6-8b29ff492d7d) ### Gitea Version 1.23.5 ### Can you reproduce the bug on the Gitea demo site? No ### Operating System _No response_ ### Browser Version FireFox
GiteaMirror added the topic/uitype/bug labels 2025-11-02 11:07:06 -06:00
Author
Owner

@wxiaoguang commented on GitHub (Mar 9, 2025):

IIRC, If you go to "self check" page, all are shown?

@wxiaoguang commented on GitHub (Mar 9, 2025): IIRC, If you go to "self check" page, all are shown?
Author
Owner

@theAkito commented on GitHub (Mar 9, 2025):

IIRC, If you go to "self check" page, all are shown?

Yes, are shown. However, this bug report issue still remains the same.

  • Why is the self check (at least the configuration self check) not under Configuration? Not intuitive. I did not know, that Self Check shows configuration errors.
  • Why does the summary under Configuration not say something like "there are errors in your configuration; please check Maintenance->Self Check section for details" or perhaps automatically redirect there or embed Configuration Self Check results on top of Configuration->Summary?
  • Problem with sending test e-mail in such a deployment state is still exactly the same. I cannot check the success or failure of a sent test e-mail (not even in Gitea log...), as it is neither shown under Configuration->Summary, nor under Maintenance->Self Check, after issuing a test e-mail.
@theAkito commented on GitHub (Mar 9, 2025): > IIRC, If you go to "self check" page, all are shown? Yes, are shown. However, this bug report issue still remains the same. * Why is the self check (at least the configuration self check) not under Configuration? Not intuitive. I did not know, that Self Check shows configuration errors. * Why does the summary under Configuration not say something like "there are errors in your configuration; please check Maintenance->Self Check section for details" or perhaps automatically redirect there or embed Configuration Self Check results on top of Configuration->Summary? * Problem with sending test e-mail in such a deployment state is still exactly the same. I cannot check the success or failure of a sent test e-mail (not even in Gitea log...), as it is neither shown under Configuration->Summary, nor under Maintenance->Self Check, after issuing a test e-mail.
Author
Owner

@wxiaoguang commented on GitHub (Mar 9, 2025):

Yes, many designs are not that good. https://github.com/go-gitea/gitea/issues/33769#issuecomment-2692996010

@wxiaoguang commented on GitHub (Mar 9, 2025): Yes, many designs are not that good. https://github.com/go-gitea/gitea/issues/33769#issuecomment-2692996010
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#14231