בטל יצירת נושאים בקטגוריית האב/שורש

סיכום מבוסס בינה מלאכותית

In a support discussion titled ‘Disable topic creation in the parent/root category,’ divyanshch asked whether it’s possible to disable topic creation in a parent category while allowing it only in subcategories — and whether a default subcategory can be assigned when users attempt to post in the parent. awesomerobot confirmed that category security settings can restrict posting to the parent while permitting it in subcategories, referencing a meta.discourse guide. However, they clarified that there’s no built-in option to auto-assign a default subcategory — users simply see a disabled new topic button in the parent category, which becomes active only when they navigate to a permitted subcategory. The composer also prevents selection of the parent if the user lacks permission, and selecting ‘New Topic’ from a subcategory page auto-populates that subcategory. awesomerobot acknowledged this UX could be improved for clarity. divyanshch confirmed the solution worked for their needs. Later, Juan_David_Martínez noted that a related improvement was implemented and merged via PR #21228.

Is possible to disable topic creation in the parent category and only allow it under sub-categories?
Also, can we assign a default sub-category whenever user tries to create a topic in the parent category?

Aplologies for multiple questions.

Yes, you can use category security settings to prevent users from posting to the parent category while allowing them to post to the subcategories. There’s more info on how to do that here: Understanding groups and category permissions

No, there’s not a setting for this. When posting to the parent category is disabled, users will see a disabled new topic button:

Screen Shot 2022-10-25 at 3.10.05 PM

And when they switch to a subcategory they can post to, it will become clickable:

Screen Shot 2022-10-25 at 3.10.13 PM

In the composer they’ll be unable to select the parent category if they don’t have permission to post there, and if they select “New Topic” from the subcategory page — that subcategory will already be populated.

We should consider making some improvement here on the disabled parent category — we don’t make it very clear why the button is disabled, or that a subcategory can be used. I can see why you’d want a default subcategory to be used there.

This solved our problem. Thanks for a quick turnaround.

This has been implemented and merged in this PR FEATURE: Default to subcategory when parent category does not allow posting by jdmartinez1062 · Pull Request #21228 · discourse/discourse · GitHub