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?

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.

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

[image] 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).

Core Plugin reversal procedure

Product Support

Ethsim2 (Ethan ) July 23, 2025, 8:24am 3

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

Topic		Replies	Views
How plugins moving to core is communicated Site feedback	15	1160	July 21, 2025
Improving /admin/plugins Feature	35	2509	May 15, 2018
Core plugins added to my updated site today Product Support auth-plugins	5	399	July 16, 2025
Bundling more popular plugins with Discourse core Announcements	132	12499	March 19, 2026
Rebuilds fail for anyone with discourse-narrative-bot in app.yml Product Support	8	2802	May 27, 2017

Core Plugin reversal procedure

Related topics