# When moving a solved topic to a category that disallows solutions, remove solved

**URL:** https://meta.discourse.org/t/when-moving-a-solved-topic-to-a-category-that-disallows-solutions-remove-solved/58385
**Category:** Feature
**Tags:** pr-welcome, solved, completed
**Created:** [October 14, 2015, 4:56pm UTC](https://meta.discourse.org/t/when-moving-a-solved-topic-to-a-category-that-disallows-solutions-remove-solved/58385 "2015-10-14T16:56:34Z")
**Posts on this page:** 13
**Page:** 1

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [October 14, 2015, 4:56pm UTC](https://meta.discourse.org/t/when-moving-a-solved-topic-to-a-category-that-disallows-solutions-remove-solved/58385/1 "2015-10-14T16:56:34Z")

</div>

I’ve seen this too when moving topics _out_ of a category where solved was set, any way to fix this @sam?

- When moving a topic **out** of a category with solutions, remove solved stuff

- When moving a topic **into** a category with solution, make solved possible

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [March 4, 2017, 11:13pm UTC](https://meta.discourse.org/t/when-moving-a-solved-topic-to-a-category-that-disallows-solutions-remove-solved/58385/2 "2017-03-04T23:13:42Z")

</div>

Agree, we should get this cleaned up, for now #pr-welcome

---

<div class="post-metadata">

### Author: ![bekicot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bekicot/32/116294_2.png) [@bekicot](https://meta.discourse.org/u/bekicot)
#### Post date: [March 30, 2017, 4:05pm UTC](https://meta.discourse.org/t/when-moving-a-solved-topic-to-a-category-that-disallows-solutions-remove-solved/58385/3 "2017-03-30T16:05:10Z")

</div>

Added [Trigger DiscourseEvent when topic category is changed by bekicot · Pull Request #4785 · discourse/discourse · GitHub](https://github.com/discourse/discourse/pull/4785), so that plugin can hook into `:topic_category_changed`. I think it is required in order to fix this issue.

---

<div class="post-metadata">

### Author: ![tgxworld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tgxworld/32/106117_2.png) [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [March 31, 2017, 1:54am UTC](https://meta.discourse.org/t/when-moving-a-solved-topic-to-a-category-that-disallows-solutions-remove-solved/58385/4 "2017-03-31T01:54:16Z")

</div>

Thanks for the PR @bekicot 👍

I was just curious but is it possible to avoid adding a `DiscourseEvent` trigger and just add a model callback which checks when the `category_id` has been changed?

---

<div class="post-metadata">

### Author: ![fhe](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fhe/32/113345_2.png) [@fhe](https://meta.discourse.org/u/fhe)
#### Post date: [March 9, 2018, 10:03pm UTC](https://meta.discourse.org/t/when-moving-a-solved-topic-to-a-category-that-disallows-solutions-remove-solved/58385/5 "2018-03-09T22:03:32Z")

</div>

Seems like this is still happening.

> [@codinghorror](#):
>
> When moving a topic out of a category with solutions, remove solved stuff

A topic marked as solution which is moved out of a category with solutions remains marked as solution (and cannot be unchecked as such)

---

<div class="post-metadata">

### Author: ![nildarar](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nildarar/32/331927_2.png) [@nildarar](https://meta.discourse.org/u/nildarar)
#### Post date: [December 3, 2020, 4:11am UTC](https://meta.discourse.org/t/when-moving-a-solved-topic-to-a-category-that-disallows-solutions-remove-solved/58385/6 "2020-12-03T04:11:05Z")

</div>

> When one of the replies is marked incorrectly as the correct answer, then the admin sees that the category is wrong and moves the topic to another category. The marked replay is still displayed as the correct answer, even if this feature is not enabled in the new category.  
> In these cases, the admin can not cancel the marked replay. It should change the category to where this feature is enabled. Cancel the correct answer and change the category again.

It would be a little easier if managers could cancel the correct answer in all categories (even those with this feature turned off).

---

<div class="post-metadata">

### Author: ![lindsey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lindsey/32/318210_2.png) [@lindsey](https://meta.discourse.org/u/lindsey)
#### Post date: [February 4, 2026, 1:17pm UTC](https://meta.discourse.org/t/when-moving-a-solved-topic-to-a-category-that-disallows-solutions-remove-solved/58385/7 "2026-02-04T13:17:19Z")

</div>

We have addressed this by ensuring that if a solution post is moved out of the topic, the topic returns to unsolved state.

The user that is moving the solution post is notified of the impact before they complete the move action:

 ![image](https://global.discourse-cdn.com/meta/original/4X/8/9/b/89bf7d6f7d3cc2919e48b0d9f6daac2589521b4e.png)

---

<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: [February 4, 2026, 2:20pm UTC](https://meta.discourse.org/t/when-moving-a-solved-topic-to-a-category-that-disallows-solutions-remove-solved/58385/9 "2026-02-04T14:20:21Z")

</div>

To me, that looks like a fix for [Carelessly splitting a solved post to a new topic breaks things](https://meta.discourse.org/t/carelessly-splitting-a-solved-post-to-a-new-topic-breaks-things/393989)

It doesn’t seem to fix the problem described in the OP which talks about a whole topic being moved to another category where solutions aren’t enabled, not about moving a few posts to another topic. When I move [`personal_messages:username` search filter doesn't work](https://meta.discourse.org/t/personal-messages-username-search-filter-doesnt-work/371848), which is a solved topic, to #Contribute > Feature where solutions are not allowed, the solution isn’t removed, and there is no warning.

---

<div class="post-metadata">

### Author: ![lindsey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lindsey/32/318210_2.png) [@lindsey](https://meta.discourse.org/u/lindsey)
#### Post date: [February 4, 2026, 2:25pm UTC](https://meta.discourse.org/t/when-moving-a-solved-topic-to-a-category-that-disallows-solutions-remove-solved/58385/10 "2026-02-04T14:25:12Z")

</div>

It addresses this problem:

> [@fhe](#):
>
> A topic marked as solution which is moved out of a category with solutions remains marked as solution (and cannot be unchecked as such)

But I can see there is more to the problem so we can keep this open.

---

<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: [February 4, 2026, 2:30pm UTC](https://meta.discourse.org/t/when-moving-a-solved-topic-to-a-category-that-disallows-solutions-remove-solved/58385/11 "2026-02-04T14:30:04Z")

</div>

Hmm, I still don’t understand. Isn’t that what I just tried?

> A topic marked as solution

I chose this topic that was marked as solved [`personal_messages:username` search filter doesn't work](https://meta.discourse.org/t/personal-messages-username-search-filter-doesnt-work/371848)

> which is moved out of a category with solutions

I moved it to #Contribute > Feature where solutions are not enabled

> remains marked as solution (and cannot be unchecked as such)

And it was still marked as solved. What did the fix change in this process?

---

<div class="post-metadata">

### Author: ![lindsey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lindsey/32/318210_2.png) [@lindsey](https://meta.discourse.org/u/lindsey)
#### Post date: [February 4, 2026, 2:38pm UTC](https://meta.discourse.org/t/when-moving-a-solved-topic-to-a-category-that-disallows-solutions-remove-solved/58385/12 "2026-02-04T14:38:50Z")

</div>

Sorry, I see what you’re saying now. I was reading this wrong, as a _post_ marked as solution which is moved out of a category.

I’ll queue this one up to fix, though, because I think it should be a small enhancement to the work we did with the solved post.

---

<div class="post-metadata">

### Author: ![lindsey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lindsey/32/318210_2.png) [@lindsey](https://meta.discourse.org/u/lindsey)
#### Post date: [February 17, 2026, 8:16pm UTC](https://meta.discourse.org/t/when-moving-a-solved-topic-to-a-category-that-disallows-solutions-remove-solved/58385/13 "2026-02-17T20:16:17Z")

</div>

We’ve updated this behavior so that when a solved topic is moved to a category that does not support solutions, the accepted solution will be removed from the topic. We’ll notify admins of this before they complete the move:

 ![CleanShot 2026-02-17 at 15.15.32](https://global.discourse-cdn.com/meta/original/4X/8/b/5/8b5c6cbc20c67fb8f732adbf7b3f67ead37f4cc8.png)

---

<div class="post-metadata">

### Author: ![lindsey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lindsey/32/318210_2.png) [@lindsey](https://meta.discourse.org/u/lindsey)
#### Post date: [February 20, 2026, 1:00pm UTC](https://meta.discourse.org/t/when-moving-a-solved-topic-to-a-category-that-disallows-solutions-remove-solved/58385/14 "2026-02-20T13:00:18Z")

</div>

This topic was automatically closed after 2 days. New replies are no longer allowed.
