I've spent some talking with a member of DNN Corp this morning about some various issues and questions with Active Social.  One problem is with Host Accounts.  Keep in mind that Active Social depends on the DNN Profile for all profile data.  A host account does not use the profile data for the portal.  This means that a host account will not be able to participate in groups.  I don't see this as problem because I have always recommended not to use Host Accounts for normal participation within your site.  However, I know this question will come up.  The answer is Host Accounts are not supported for Profiles or Groups within Active Social.

We were also having a few other issues that we were trying to workaround.  The best option is for us to raise the minimum DNN version from 4.5 to 4.6.  We are still testing to make sure 4.6 contains the code we need.  Hopefully we will not need to go any higher.

Thanks,
Will

The issue of hosts not being able to do things is quite acceptable in my opinion.  We have the same issue with Catalookstore - you need to be logged in as admin to do a transaction, and if I'm correct, are there some elements of ventrians modules that are only for host it varies slightly with host (I could be wrong on that one)

I think you're going to find that in the future - builds in the 4.5 > 4.8 space are going to be quirky with some changes that occured.  It reminds me of the 3.2.2 build - that was one I wish never came out.

There are elements of host account behaviour that I like as well because it does allow for some 'super user' configurations that might be related to how you run your builds, or options you wish to provide across the board.  

Just my opinion, but it seems quite fine to me.

Nina

I'm cool with this too. as a matter of practice I never us my host account to participate as a member on my sites. Too much of a security risk and somewhat confusing sometimes. Also - Nina mentioned it but there are a number of modules that have this limitation. It makes sense and it really doesn't impact the operation or maintenance of a site.

Just out of curiosity, does this also apply to portal admin accounts that had the IsSuperUser tag modified to let them act as host accounts? The local portal profile should already have been created in that case, but is there anything else that might cause problems?

I do the same thing with the ST modules - the Host account can never post new content.