I was actually wrong… I do have some templates, but those are for specific categories, not Uncategorized (I saw that via the link shared by @Moin).
But now I noticed something, which defeats everything I’ve done so far:
If I’m in the home page and I click NEW TOPIC, I can see the option to pick a category, but if I’m inside a category, the dropdown is automatically populated with that category, which is something I wanted to avoid. Is this even possible, to achieve this regardless of where the user is?
Just because someone is in the “General” category, for example, that doesn’t mean a new topic is meant to be in that category, but if the user doesn’t see that, they might create a topic in the wrong category.
Ah, yes. A topic template on any category will switch the composer behaviour. I was asking about Uncategorised in particular just in case there was an overlooked bug/ux issue (thankfully that doesn’t appear to be the case )
For your topic creation flow itself, I think I would initially trust users to make the right choices and then maybe adapt things if you notice a significant problem crop up.
So let me see if I understand it: are you saying that by having a template associated with at least one category, when the default is “no category” (in this case it seems to be when I’m not inside any particular category), is locks the composer?
This is actually more related to them not noticing that the category is wrong, more than an actual “wrong decision”. It can be overlooked. For example, sometimes in the Keyboard Maestro forum, I add the title and the message and hit Submit to then see the alert to pick a category. It’s just that instinct that the most important things are the Title and the Message. I guess my brain just assumes that my message is being sent to the “Help” category.
So, if it happens to me, I can see how that can happen to others as well, so always forcing them to pick a category, would be safer.
But would this even be possible to bypass that behavior where it picks the current category automatically?
Good to know that this is not a bug, then.
In that case, I’m happy with the script I have, at least for the “no category” option.
Thank you for the tip. I will keep that in mind. For now, I’m just trying to work on things that are truly relevant. This is just a minor detail and probably will require more work than expected and since I’m still building it (no users yet), it’s not a priority.
One thing you may want to double check is creating a new topic, adding some text to the composer without picking a category, and then picking the category with the topic template.
I’m hoping it will simply not show you the topic template, but I also had a doubt about whether the topic template would overwrite the existing user added text instead. Hopefully a nothing-burger.
I was asking about Uncategorised in particular just in case there was an overlooked bug/ux issue (thankfully that doesn’t appear to be the case 
)
