I verified that this is resolved by DEV: remove and replace Uncategorized - Pull Request #41169 - discourse/discourse - GitHub (Removing Uncategorized and migrating to a standard category).
Kudos to @sam for looking beyond the specific faults described here to see the bigger picture of the unnecessary complexity introduced by having a special type of category that could just as well be served by a standard category.
Something that might be confusing is that the removal is controlled by a feature flag, which is only accessible if you have the old special Uncategorized category enabled:
So if you have the allow uncategorized topics setting disabled, your forum will currently still be subject to the bug reported here, even after it has been updated to the version of Discourse that contains the DEV: remove and replace Uncategorized - Pull Request #41169 - discourse/discourse - GitHub changeset.
I was able to resolve the bug reported here on my forum by the following procedure:
- Enable the
allow uncategorized topicssetting in the site settings. - Enable Remove and replace Uncategorized category in “Upcoming changes”.
- Delete the “Uncategorized” category that was created as a result of step 2.