Tim, the module was never designed for multiple instances in a single portal. There are a few reasons it was done this way. One of the main reasons right now is the grouping and ability to show only a single group on one page and still control all other aspects from one module. Another huge reason is the tie in w/ the community. This module is not module specific, to be clear. The issues you are experiencing are not going to go away easily, but do remember that single user moderator assignments and private forums are definately done on the forum level and shouldn't be a huge ordeal and if there is a problem around those two, then I need to investigate.

Tim, not taking it as an insult as everyone has their own opinion, but to say a module is beta/alpha because it doesn't meet your requirement is a bit much.

Just to be clear:

a - This might be the case. I don't undrstand why you need multiple instances of this module on the same portal, let alone the same page. (I can perhaps see why it might be possible to have more than one per site) If you have two on the same page, based on how this module goes beyond normal dnn control loading it is going to show some odd behavior. From what I have seen, it doesn't break it just shows some quirks in some of the examples. Doing this shouldn't even break it but I definately dont' test for this.

b - I never said you couldn't do this. As you can see, you are not using a single 1 per install.

c - This is not supposed to be the case. I am waiting to see your example.

I think we are having some communication issues here. I am waiting for you demo/example. To continue to feed info on the topic w/ the hope of others understanding things:

The forum only creates one record per userid in the forum_users table. This means all attributes for the specific user are shared. In most cases this means nothing as someone would probably have the same preferences. There are other items like IsTrusted that this becomes an issue. Before DNN version 3.3.3 or greater I only had the option of duplicating the userid, which is not good. Now, I have the option of storing most of this data in the user profile of the core.

I am about finished w/ a permissions re-write and notification backend re-write that I am testing and changing so there are no multi-portal, or multi-module usage issues here. As for the user specific possible issues, as I said this should go away with moving user data to user profile.

Obviously I am going to have to duplicate this issue to correct it but...

Anyone who is tab admin or site admin will be able to review all forums. Now that I think about it and think of how this is probably happening, this is someting I need to correct. I need to make sure that moderated forums are tied to at least portalid, if not moduleid. (I will probably use ModuleID).

I am not sure how I am going to handle the moderator bit. The problem here is avoiding a huge performance hit doing a lookup for each user when they first hit the forum (as I can cache it after that).