# Plugin Cleaner

**URL:** https://meta.discourse.org/t/plugin-cleaner/399505
**Category:** Plugin
**Created:** [March 29, 2026, 2:10am UTC](https://meta.discourse.org/t/plugin-cleaner/399505 "2026-03-29T02:10:32Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [March 29, 2026, 7:24am UTC](https://meta.discourse.org/t/plugin-cleaner/399505/2 "2026-03-29T07:24:32Z")

</div>

Nice intent.

A few challenges:

- Many good plugins create and manage their own tables. Looking at your code, I’m not sure you’ve taken account of that yet?

- I don’t see a way your plugin protects the user from deleting the custom fields outside of a specific plugin they might want to “cleanse” - you are relying on the user to identify them? Just blocks deleting custom fields that are in core?

And on that note:

> <https://github.com/canbekcan/discourse-plugin-cleaner/blob/65e7f7eb2b11badf0de31046601e729c84c8dc2f/lib/plugin_cleaner/scanner.rb#L6>

That looks a little risky. What if a core upgrade adds new ones that you don’t catalogue - are you going to risk deleting new core fields that you are not explicitly listing?

In any case I wish you luck with development, it’s definitely an interesting addition.

---

_[View the full topic](https://meta.discourse.org/t/plugin-cleaner/399505)._