# Hiding old plugins, themes and components
**URL:** https://meta.discourse.org/t/hiding-old-plugins-themes-and-components/318744
**Category:** Site feedback
**Created:** [July 27, 2024, 7:07am UTC](https://meta.discourse.org/t/hiding-old-plugins-themes-and-components/318744 "2024-07-27T07:07:21Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [July 27, 2024, 7:07am UTC](https://meta.discourse.org/t/hiding-old-plugins-themes-and-components/318744/1 "2024-07-27T07:07:21Z")
Continuing the discussion from [Warning about broken and deprecated plugins, components and themes](https://meta.discourse.org/t/warning-about-broken-and-deprecated-plugins-components-and-themes/318742):
Should broken and deprecated plugins, components and themes be hidden from listings? Or should/could we have similar automatic than what WordPress is using when warning if a plugin hasn’t updated in three years?
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [July 27, 2024, 7:27am UTC](https://meta.discourse.org/t/hiding-old-plugins-themes-and-components/318744/2 "2024-07-27T07:27:15Z")
> [@Jagster](#):
>
> Should broken and deprecated plugins, components and themes be hidden from listings?
We have the #broken, #deprecated, #end-of-life, and #unmaintained tags default muted so the topics don’t appear in topic lists unless you interact with the topic (or change the notification level manually), but they are still findable by search so they’re not completely disappeared.
> [@Jagster](#):
>
> warning if a plugin hasn’t updated in three years?
I think I’ve seen a few plugins that haven’t been updated in a number of years, but only because they didn’t need to be and were still working perfectly well. But even if that’s something we wanted to highlight on the plugin topic, we would need some way of pulling the last update date from GitHub.
---
### Author:  [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [July 27, 2024, 7:37am UTC](https://meta.discourse.org/t/hiding-old-plugins-themes-and-components/318744/3 "2024-07-27T07:37:09Z")
I’m quite sure I haven’t unmuted those. Or if you guys have changed that behaviour you didn’t let it happend to everyone? I have to re-check my settings.
But if muting is there then it does what I asked.
That unmaintained question as an automatic action would be useful feature, though.
**edit**
Nope, those tags isn’t muted for me. But that isn’t any issue for me, because I can live with it and I know how tags work, even muting.
---
### Author:  [@Heliosurge](https://meta.discourse.org/u/Heliosurge)
#### Post date: [July 27, 2024, 10:39pm UTC](https://meta.discourse.org/t/hiding-old-plugins-themes-and-components/318744/4 "2024-07-27T22:39:36Z")
> [@JammyDodger](#):
>
> We have the #broken, #deprecated, #end-of-life, and #unmaintained tags default muted so the topics don’t appear in topic lists unless you interact with the topic (or change the notification level manually), but they are still findable by search so they’re not completely disappeared.
That is cool for sure. Wondering though if maybe a suggested idea to color these posts similar to Solved plugin where you can have it highlight the post in Red for unsolved? For when seen using search?
Maybe even a highlight color when merged with core. Took awhile but did figure out quite awhile back had missed Chat being merged with core and it caused me to have some minor downtime.
Alternatively if using bbcode colours. A notice in the Op post top could use a specialize background color or similar customized quote like solved like idea.
Imagine a #Customization > Theme component could be made that inserts a banner in the top of the Op based on tag as well. So saves editing Op topics