The discussion addresses a bug where moving a solved topic to a category that disallows solutions failed to remove the “solved” status. codinghorror initially reported the issue, noting that topics moved out of categories with solutions retained their solved markers. sam agreed to the cleanup, and bekicot submitted a PR adding a plugin hook to handle category changes. tgxworld suggested using a model callback instead of a new event trigger. fhe and nildarar confirmed the issue persisted, explaining that admins could not uncheck the solution after moving the topic to an incompatible category. lindsey initially claimed a fix was in place, but Moin clarified that the previous fix only addressed moving individual posts, not entire topics. lindsey acknowledged the misunderstanding and lindsey committed to fixing the topic-level issue. Finally, lindsey confirmed the behavior was updated: when a solved topic is moved to a category without solution support, the accepted solution is automatically removed, and admins receive a notification before the move is completed.
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?
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).
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, which is a solved topic, to Contribute > Feature where solutions are not allowed, the solution isn’t removed, and there is no warning.
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: