# Core Plugin reversal procedure

**URL:** https://meta.discourse.org/t/core-plugin-reversal-procedure/375307
**Category:** Support
**Created:** [July 22, 2025, 8:43pm UTC](https://meta.discourse.org/t/core-plugin-reversal-procedure/375307 "2025-07-22T20:43:42Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Ethsim2](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ethsim2/32/522255_2.png) [@Ethsim2](https://meta.discourse.org/u/Ethsim2)
#### Post date: [July 22, 2025, 8:43pm UTC](https://meta.discourse.org/t/core-plugin-reversal-procedure/375307/1 "2025-07-22T20:43:42Z")

</div>

Given the recent wave of core plugins, where root users have needed to either comment out or remove lines of their `app.yml`

if a core plugin were to no longer be a core plugin, how would the user know to add / uncomment the lines? would their be an admin UI notice for any plugin in core to move out of core?

---

<div class="post-metadata">

### Author: ![Heliosurge](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/heliosurge/32/571810_2.png) [@Heliosurge](https://meta.discourse.org/u/Heliosurge)
#### Post date: [July 22, 2025, 10:47pm UTC](https://meta.discourse.org/t/core-plugin-reversal-procedure/375307/2 "2025-07-22T22:47:57Z")

</div>

Interesting question. In my time of using discourse. I don’t recall any plugins that waa merged with core being removed from core at a later date

However imagine similar to announcement of them being merged; there would be one to announce it being removed and how to re add it if needed.

---

<div class="post-metadata">

### Author: ![Ethsim2](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ethsim2/32/522255_2.png) [@Ethsim2](https://meta.discourse.org/u/Ethsim2)
#### Post date: [July 23, 2025, 8:24am UTC](https://meta.discourse.org/t/core-plugin-reversal-procedure/375307/3 "2025-07-23T08:24:48Z")

</div>

Interesting reply. However, without sophisticated scanning of the database for “plugin requirement”, there would be no “HINT” that many users relied on during the failed rebuild processes

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [July 23, 2025, 8:39am UTC](https://meta.discourse.org/t/core-plugin-reversal-procedure/375307/4 "2025-07-23T08:39:12Z")

</div>

We are not planning to reverse our decision so you don’t need to worry about this.

---

<div class="post-metadata">

### Author: ![Heliosurge](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/heliosurge/32/571810_2.png) [@Heliosurge](https://meta.discourse.org/u/Heliosurge)
#### Post date: [July 23, 2025, 12:31pm UTC](https://meta.discourse.org/t/core-plugin-reversal-procedure/375307/5 "2025-07-23T12:31:50Z")

</div>

> [@Ethsim2](#):
>
> Interesting reply. However, without sophisticated scanning of the database for “plugin requirement”, there would be no “HINT” that many users relied on during the failed rebuild processes

The only issue I had once was missing that Chat plugin was merged with core. So the rebuild failed due to trying to install the Chat plugin. Once a plugin is merged with core it shouldn’t cause a rebuild issue. Any issue after the Merge should be either a new plugin failure or attempting to install a core plugin(twice).
