# 清理建议实际上并未清理

**URL:** https://meta.discourse.org/t/clearing-advice-doesnt-actually-clear-it/398754
**Category:** UX
**Tags:** fixed
**Created:** [2026年三月18日 19:34 UTC](https://meta.discourse.org/t/clearing-advice-doesnt-actually-clear-it/398754 "2026-03-18T19:34:57Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![darkpixlz](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/darkpixlz/32/549896_2.png) [@darkpixlz](https://meta.discourse.org/u/darkpixlz)
#### Post date: [2026年三月18日 19:34 UTC](https://meta.discourse.org/t/clearing-advice-doesnt-actually-clear-it/398754/1 "2026-03-18T19:34:57Z")

</div>

为了提供上下文，我的测试站点位于运行在我家庭实验室中的反向代理后面，因为我没有无限的 IP。我已将其转发到端口 80，因为它有效，而且我不想弄坏任何东西。

![image](https://cdck-file-uploads-global.s3.dualstack.us-west-2.amazonaws.com/meta/original/4X/3/a/6/3a6dc913feb113a5b0ee2d70b36a49866fb6b4b5.png)

但这篇帖子不是“修复我的代理设置”的支持帖，我注意到的一件事是，无论我多少次告诉此通知消失，它总会回来：

 ![image](https://global.discourse-cdn.com/meta/original/4X/8/8/5/88544d57754d6c7be43403216207c93ccb4dfb47.jpeg)

“关闭”按钮的工作不就是……关闭消息吗？

---

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [2026年三月18日 19:50 UTC](https://meta.discourse.org/t/clearing-advice-doesnt-actually-clear-it/398754/2 "2026-03-18T19:50:59Z")

</div>

如果您有有效的 SSL，您可以将 `force_https` 设置为 `true`，此警告就会消失。此警告仅在重建后或从新浏览器访问时显示（因此我们假设忽略是基于 cookie 的）。在您的情况下，看起来您的反向代理已经终止了 SSL，因此您可以安全地在 Discourse 中启用强制 HTTPS。

---

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [2026年三月18日 20:57 UTC](https://meta.discourse.org/t/clearing-advice-doesnt-actually-clear-it/398754/3 "2026-03-18T20:57:26Z")

</div>

> [@darkpixlz](#):
>
> “忽略”按钮的作用不就是忽略消息吗？

不完全是

> [@ted](#):
>
> 但是，如果根本问题没有修复，那么当您重新加载页面时，它还会再次出现。
> 
> 这是已知行为。当前的功能是用来消除“卡住的”或一次性的通知。我们正在努力扩展此功能，以便您可以将这些通知“小睡”一段时间，这样它们就不会立即再次出现。

---

<div class="post-metadata">

### Author: ![ted](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ted/32/283882_2.png) [@ted](https://meta.discourse.org/u/ted)
#### Post date: [2026年四月6日 01:42 UTC](https://meta.discourse.org/t/clearing-advice-doesnt-actually-clear-it/398754/4 "2026-04-06T01:42:10Z")

</div>

我已提交一个 PR，如果合并，将允许您真正忽略来自特定问题检查的通知，并新增一个仪表板标签页，您可以在其中查看所有检查的状态并取消忽略。

> <https://github.com/discourse/discourse/pull/39103>
>
> \## Background
> 
> Currently you can "dismiss" problem checks on the dashboard, bu…t if the problem persists it will show up again on the next reload, which is confusing.
> 
> There was previously some discussion about adding a feature to "snooze" problem checks, but I think even with that it remains a bit too opaque. You'd need to spelunk around in the console to try and figure out what is going on.
> 
> \## What is this change?
> 
> This PR does a couple of things:
> 
> \### 1. Replace Dismiss with Ignore
> 
> Hitting ignore will prevent the problem check from creating new admin notices until it has been unignored from the new problem checks page.
> 
> \*\*Screenshot\*\*
> 
> \<img width="395" height="61" alt="Screenshot 2026-04-05 at 4 37 39 PM" src="https://github.com/user-attachments/assets/4816fd04-046b-441e-9471-c160dd3f82b9" /\>
> 
> \### 2. Add a new problem check page
> 
> This page provides a list of problem checks with information on whether they are passing or failing, and when they were last run. You can also ignore or unignore (watch) problem checks from here.
> 
> \*\*Screenshot\*\*
> 
> \<img width="600" height="200" alt="Screenshot 2026-04-05 at 4 26 37 PM" src="https://github.com/user-attachments/assets/d8cb2b6a-3f56-409c-97f0-312cb1545654" /\>
> 
> \### 3. Remove the problem check timestamp from the dashboard
> 
> This timestamp made sense under the previous model, where all checks were run at once and the results cached. With the new model, there's a mix of on-demand and scheduled checks, and having a single timestamp is misleading at best. In practice it's always going to be just the timestamp when you last loaded the dashboard.
> 
> \*\*Before\*\*
> 
> \<img width="240" height="100" alt="Screenshot 2026-04-05 at 4 30 21 PM" src="https://github.com/user-attachments/assets/1846e024-0042-476e-8b5d-41b6745af75f" /\>
> 
> \*\*After\*\*
> 
> \<img width="210" height="95" alt="Screenshot 2026-04-05 at 4 29 19 PM" src="https://github.com/user-attachments/assets/a39c87c1-c1e3-4621-8219-e3903ba2ada4" /\>

请注意，此功能需经 Discourse 工作人员（例如 @kris.kotlarek）审核并合并。🙂

---

<div class="post-metadata">

### Author: ![kris.kotlarek](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/kris.kotlarek/32/176919_2.png) [@kris.kotlarek](https://meta.discourse.org/u/kris.kotlarek)
#### Post date: [2026年四月23日 00:30 UTC](https://meta.discourse.org/t/clearing-advice-doesnt-actually-clear-it/398754/5 "2026-04-23T00:30:29Z")

</div>

谢谢，@ted，你的 PR 👏  
我刚合并了它 🤩

---

<div class="post-metadata">

### Author: ![darkpixlz](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/darkpixlz/32/549896_2.png) [@darkpixlz](https://meta.discourse.org/u/darkpixlz)
#### Post date: [2026年四月26日 00:31 UTC](https://meta.discourse.org/t/clearing-advice-doesnt-actually-clear-it/398754/6 "2026-04-26T00:31:22Z")

</div>

此主题在最后一次回复后 3 天自动关闭。不再允许新的回复。
