# Core Plugin reversal procedure

**URL:** <https://meta.discourse.org/t/core-plugin-reversal-procedure/375307>\
**Category:** Product 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:** 1\
**Showing post:** 5

<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).

---

_[View the full topic](https://meta.discourse.org/t/core-plugin-reversal-procedure/375307)._