I was curious to test how MonoX could be implemented at multiple levels of the same domain.
instance 1: domainname.com
instance 2: SubDomain1.domainname.com (indepentant CMS structure, but same membership info/db as root domain.)
instance 3: SubDomain2.domainname.com (indepentant CMS structure, but same membership info/db as root domain.)
I understand how to manipulate the providers, but installing all three instances to separate databases and then manipulating the membership providers still leaves the task of trying to keep users/roles synchronized between the three databases. It just seemed that the way it was worded in the user manual, the 'now removed' option sounded as though it had done exactly what I was wanting to test....maintain information on multiple installed instances, based on domain, and hopefully be able to simply specify whether they should share membership data or not(MojoPortal does this well).