# 表格构建器更新后无法使用

**URL:** https://meta.discourse.org/t/table-builder-not-working-after-an-update/279019
**Category:** Bug
**Tags:** table-builder
**Created:** [2023年八月20日 02:40 UTC](https://meta.discourse.org/t/table-builder-not-working-after-an-update/279019 "2023-08-20T02:40:39Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Lilly](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lilly/32/575047_2.png) [@Lilly](https://meta.discourse.org/u/Lilly)
#### Post date: [2023年八月20日 02:40 UTC](https://meta.discourse.org/t/table-builder-not-working-after-an-update/279019/1 "2023-08-20T02:40:39Z")

</div>

看起来这次提交可能破坏了表格构建器和我的网站。论坛离线且无法加载，并且我在控制台中看到了关于表格构建器组件的错误。

我通过禁用该组件在安全模式下恢复了论坛。仪表板提示我更新 TC，所以我更新了。糟糕！

> <https://github.com/discourse/discourse/pull/23148>
>
> Manipulating theme module paths means that the paths you author are not the ones… used at runtime. This can lead to some very unexpected behavior and potential module name clashes. It also meant that the refactor in 16c6ab8661b38051b14d68297afdc8504bc1175b was unable to correctly match up theme connector js/templates.
> 
> While this could technically be a breaking change, I think it is reasonably safe because:
> 
> 1. Themes are already forced to use relative paths when referencing their own modules (since they're namespaced based on the site-specific id). The only time this might be problematic is when theme tests reference modules in the theme's main \`javascripts\` directory
> 
> 2. For things like components/services/controllers/etc. our custom Ember resolver works backwards from the end of the path, so adding \`discourse/\` in the middle will not affect resolution.

---

<div class="post-metadata">

### Author: ![leomakkinje](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/leomakkinje/32/63366_2.png) [@leomakkinje](https://meta.discourse.org/u/leomakkinje)
#### Post date: [2023年八月21日 12:34 UTC](https://meta.discourse.org/t/table-builder-not-working-after-an-update/279019/2 "2023-08-21T12:34:30Z")

</div>

> [@Lilly](#):
>
> 看起来这个提交可能破坏了表格生成器和我的网站。

我可以确认更新表格生成器会破坏 Discourse。主页卡在显示“正在加载…”指示符。安全模式然后禁用表格生成器可以解决此问题。

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [2023年八月21日 12:42 UTC](https://meta.discourse.org/t/table-builder-not-working-after-an-update/279019/3 "2023-08-21T12:42:42Z")

</div>

您需要使用最新版本的 Discourse 才能更新或安装最新版本的 Table Builder。如果您从 `/admin/upgrade` 页面进行更新，应该可以重新启用 Table Builder。 👍

---

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [2023年八月21日 13:24 UTC](https://meta.discourse.org/t/table-builder-not-working-after-an-update/279019/4 "2023-08-21T13:24:53Z")

</div>

抱歉造成了干扰！我刚刚在 [table-builder](https://github.com/discourse/discourse-table-builder/commit/ac73eda7107ab7adb07d4263597e7c38a84f8564) 中添加了一个修复程序，以便可以在旧版本的 Discourse core 上安全地更新它。

@leomakkinje 如果您再次更新 table-builder 然后重新启用，事情应该会好很多。

---

<div class="post-metadata">

### Author: ![leomakkinje](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/leomakkinje/32/63366_2.png) [@leomakkinje](https://meta.discourse.org/u/leomakkinje)
#### Post date: [2023年八月21日 13:27 UTC](https://meta.discourse.org/t/table-builder-not-working-after-an-update/279019/5 "2023-08-21T13:27:55Z")

</div>

感谢您的快速跟进！

与此同时，我已将网站升级到最新的 Discourse 版本，现在一切都已就绪。

---

<div class="post-metadata">

### Author: ![Canapin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/canapin/32/119591_2.png) [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [2023年九月14日 14:28 UTC](https://meta.discourse.org/t/table-builder-not-working-after-an-update/279019/6 "2023-09-14T14:28:14Z")

</div>