Enabled it. Did not work.

Oh, crap. It looks like I haven't created a README, have I? This must be the only module of mine that I didn't do that for.

Anyway, this is a CCK field, so you add it to your content types as a new field, you don't add it via the category interface like a regular taxonomy. In fact, you want to UNCHECK the taxonomy from being directly associated with content types in the usual way.

I'll whip up a README shortly and upload it. Sorry for the oversight. Note, this module's regular behavior is to keep term associations in a cck table, not in the term_node table. This will make the terms hidden from the taxonomy module and not operate like regular tags. There are use cases for that. However, I have included a checkbox to make the terms get added to term_node so you can have 'regular' taxonomy behavior as well. It's your option.

So, enable the module, create a taxonomy to use, create or modify a content type, add a cck field containing the taxonomy displayed with cck_TSSU, adjust the settings, save, create content.

Hope that clears things up. I'll get on that README. Thanks for the heads-up.

Readme is uploaded and will be in the next tarball. In a moment, I'll also add a link from the project page. Mark this issue as fixed if this all does it for you.

Thanks for the compliment. I find I have the same frustration with other modules. Which is one reason I try to do good docs as well. Not sure how I missed it on this project in the first place. I still need to update the og_forum docs. I didn't write them in the first place. Very not-helpful.

I'll mark this as fixed then.

As for radio buttons. I will when I have the time. The problem is, I'm starting a business and wearing a dozen or more hats. As I get the biz off of the ground, it will get worse before it gets better. And with the nature of what I'm endeavoring to do, I'll need to hire support and sales people before programmers. But once I have a certain number of clients and the support and sales positions filled, that will give me more time to do additions on modules like this one that are not necessary for my use, but which are obvious and useful for general users. I'm committed to Drupal for the long haul. I anticipate literally dozens of modules to come out of my company's development that can be used by the community. A few will have to stay in-house to protect some IP, but most will be public. And of course, that helps me with testing and finding bugs, so it's a win-win. Which is why supporting users like you is important and why I spend a good portion of my time doing so.