Hi Will,

Thanks so much for looking into this. I know there a many thorny issues with RoleID solutions, cookie limits in the browser, etc. I really don't have any ideas on how to fix this. Maybe explore how other portal frameworks solve this problem. Good luck.

Concerning Active Social, I saw you mention "Active Social doesn't require role security for groups. It is a configuration option, and not recommended for the exact reasons outlined in this issue.".

Is this an option available now, if we have limited groups/roles? How would I configure this?

Thanks,
Chris

---

Chris Wylie
Chief Executive Officer

1775 W. State Street Suite 371, Boise ID 83702 USA
 

While I have the attention of such august company, please take a look at this issue:
Profile Namespace Bug causing DNN crash:
http://www.dotnetnuke.com/Resources/Forums/forumid/118/threadid/434350/scope/posts.aspx
http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=18476&PROJID=2

If the the namespace of an object serialized in a Profiledata column of the Profile table no longer exists (a module has been uninstalled), or its namespace xml structure has changed (for whatever reason) then DNN crashes if certain users try to log back into the system after an upgrade (user's that were "in state" during the upgrade). The User account then has to be deleted and restored to recalibrate or we have to run a SQL script: delete * from Profile to dump this in state profile data and allow the user free access to the site again.

DNN should instead, just gracefully ignore the inconsistency.

We have seen this present recently in sites that run our LMS and other DNN sites running other third party module (without our LMS).

We are hoping for some attention to what we consider a consequential bug. I apologize for the tangent. Any comments on this issue should be on the linked thread, not this one.

Thanks,
Chris

---

Chris Wylie
Chief Executive Officer

1775 W. State Street Suite 371, Boise ID 83702 USA