The discussion revolves around the procedure for reversing the inclusion of a plugin into Discourse core. Ethsim2 initiated the conversation, questioning how users would be informed to re-add lines to their app.yml files if a core plugin were to be removed from core, particularly referencing failed rebuild processes due to missing plugin requirements Ethsim2. Heliosurge notes they don’[#375307/2]t recall a core plugin ever being removed after merging and suggests an announcement similar to the merge announcement would be needed. Heliosurge also recounts an issue where a rebuild failed after the Chat plugin was merged into core, due to attempting to install it again. However, the main point is that sam states that reversals of this decision are not planned, meaning the scenario is unlikely to occur.
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.
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
We are not planning to reverse our decision so you don’t need to worry about this.
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).