# Combining Category types

**URL:** https://meta.discourse.org/t/combining-category-types/409045
**Category:** Feature
**Tags:** solved, topic-voting, events
**Created:** [August 1, 2026, 2:05pm UTC](https://meta.discourse.org/t/combining-category-types/409045 "2026-08-01T14:05:24Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![ecki](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ecki/32/264025_2.png) [@ecki](https://meta.discourse.org/u/ecki)
#### Post date: [August 1, 2026, 2:05pm UTC](https://meta.discourse.org/t/combining-category-types/409045/1 "2026-08-01T14:05:25Z")

</div>

I can assign multiple types to a single category, but that doesnt work very well:

- all posts are marked as unresolved if support+mark is turned on, the user cant specify they have a support request
- all posts show “vote 0”, even when the user can mark a post as up for voting (it should only show 0 votes for the one who opted into this.
- When i enable events the category is replaced by a giant calendar, while this may be ok in some occassions a normal discussion group with a small calender sidebar widget would be more helpful so i can mark only a few posts as having a date.

---

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [August 1, 2026, 2:13pm UTC](https://meta.discourse.org/t/combining-category-types/409045/2 "2026-08-01T14:13:22Z")

</div>

How did you use the solved, topic voting, and event plugin before those became category types? While the process of configuring those plugins for a category has changed I cannot recall that the features have changed.

Did you use those on the categories before too? Or are you just trying them for the first time? I wonder how users indicated that their topic is a support request before.

---

<div class="post-metadata">

### Author: ![ecki](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ecki/32/264025_2.png) [@ecki](https://meta.discourse.org/u/ecki)
#### Post date: [August 20, 2026, 1:46am UTC](https://meta.discourse.org/t/combining-category-types/409045/3 "2026-08-20T01:46:45Z")

</div>

I am just trying them out, I wanted to Set up a Product idea voting Category. I would like the topic voting and private comment Style however better.. I learned now there is no Category to enforce that. But on the other hand, I could mix them with normal Posts, that’s also good. Just need to Train the users to actually use them (or allow the moderator to turn a post into a idea vote (vote post) post then.. hm.

---

<div class="post-metadata">

### Author: ![satonotdead](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/satonotdead/32/447830_2.png) [@satonotdead](https://meta.discourse.org/u/satonotdead)
#### Post date: [August 20, 2026, 4:15am UTC](https://meta.discourse.org/t/combining-category-types/409045/4 "2026-08-20T04:15:13Z")

</div>

I thought of something similar, but focused exclusively on support. Features could receive voting, while technical posts would receive solutions.

Creating two categories is counterproductive for users; for now, I don’t plan to enable them as they are, precisely for this reason.

The dream: an initial form when publishing would classify the posts, and then each would receive the appropriate functionality 🙂

---

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [August 21, 2026, 9:59am UTC](https://meta.discourse.org/t/combining-category-types/409045/5 "2026-08-21T09:59:43Z")

</div>

I think you could use tags for that. Then you enable solutions based on a #question tag and make that also hide the voting on those topics with css, like it’s done on #feedback topics here on Meta.  
You could combine that with a #form-templates that helps with the tag selection.

---

<div class="post-metadata">

### Author: ![ecki](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ecki/32/264025_2.png) [@ecki](https://meta.discourse.org/u/ecki)
#### Post date: [September 5, 2026, 10:05pm UTC](https://meta.discourse.org/t/combining-category-types/409045/6 "2026-09-05T22:05:49Z")

</div>

Oh can you actually make solution types based on a tag? Something like „mark it a support question“? That would be cool so discussion entries have no „Me too“ or „mark solved“ buttons

---

<div class="post-metadata">

### Author: ![satonotdead](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/satonotdead/32/447830_2.png) [@satonotdead](https://meta.discourse.org/u/satonotdead)
#### Post date: [September 5, 2026, 10:16pm UTC](https://meta.discourse.org/t/combining-category-types/409045/7 "2026-09-05T22:16:29Z")

</div>

I am agree with this fusion, some topics should have the ‘Me too’ option and voting as well. I think it should be switchable for enabling both, one or none of them.

Not sure how to properly handle it but the purpose is really supported here.

---

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [September 5, 2026, 10:16pm UTC](https://meta.discourse.org/t/combining-category-types/409045/8 "2026-09-05T22:16:40Z")

</div>

There is the `enable_solved_tags` setting. But I don’t know if that supports the “me too” button.

The new reporting tool seems to be limited to the solved plugin being set up by category. This makes me wonder if other recent features are affected too.

> [@See the users and topics behind the numbers in admin reports](https://meta.discourse.org/t/see-the-users-and-topics-behind-the-numbers-in-admin-reports/411397/1):
>
> **Note:** The Accepted Solutions report and corresponding dashboard card are only shown in communities with at least one [support category](https://meta.discourse.org/t/easily-create-support-categories-using-the-discourse-solved-plugin/398338).
