The Uncategorized category was the one I always filtered out in my queries as we never enabled it since day 1, so I welcome its removal, thanks @lindsey ![]()
However, I had a rather unexpected experience today.
TL;DR; The Uncategorized category was enabled for everyone, and there were already two topics created in it.
Let me take a step back for a larger picture. Before the latest release deployed on our production last night,
- the
allow_uncategorized_topicssetting was set tofalse, - the Uncategorized category was never used and empty; practically invisible to all users.
- the Remove and replace uncategorized upcoming change was enabled for Everyone
Just because the category was never used, and empty; I expected it would be removed completely.
It might be just me misreading the feature description, but I still was surprised to see it became a public category.
I think it would helped better if there was a clearer wording, and explanation of what to expect in various configurations.
For the record, I moved the topics to another category, and changed its security settings to make it admin only. So it is not an issue at the moment.
Once I have the time, I’ll review, and eventually delete the category completely.