The discussion revolves around a bug where non-staff users can access the #uncategorized category even when it’s disabled via site settings. jomaxro reports that users can navigate to /c/uncategorized directly or via the category filter dropdown, where they can create new topics without selecting a category—contrary to expected behavior. j.jaffeux acknowledges the issue and proposes a fix via a pull request (#7922), focusing on preventing topic creation without a category selection. codinghorror and sat confirm the issue, with sat noting that while the category is not visible in search, it still appears when accessed via direct link. Stephen and schleifer argue that the behavior isn’t a bug since uncategorized is not private, but jomaxro insists the ability to create uncategorized topics without a category selection is a regression. The thread concludes with codinghorror suggesting the issue be closed if the fix is satisfactory.
The New Topic button is on the (empty) page, and lets them start composing without selecting a category, which shouldn’t be possible with the setting off. The composer should look like this:
What about this? It seems like a regression to me - with Uncategorized disabled users should be required to select a category before composing the body. However they are able to compose the body without a category if they click new topic from the uncategorized page.
Yes I fixed what was very easy for me. Need to think about the composer, if you thought we absolutely had to remove the URL, then it was solved with it. Maybe I should just redirect. Need to dig more, uncategorized has many cases and I’m unsure what this would cause.