Hi,

Currently all things are checked against roles, so the shortest path to do what you want right away is to create roles corresponding to users. I will ponder this, but nothing is coming soon for this. 

It sounds like you are trying to build a social networking site. I would caution you against letting strangers register on your site and then allow them to create or edit pages using mojoPortal features. mojoPortal features provide too much power and you should not let untrusted users have access to them on your site. Using the Html or Blog feature for example users can introduce javascript into the page and try to do xss attacks and steal cookies and try to install malware and all manner of mischief. These features were designed for trusted users who own the web site not for public users.

Best,

Joe

Jesse,

Your question was similar but about sub sites, with sub sites at least if using different host names for the sites they would have independent logins and content and no malicious script from one can get to the other so there is not so much risk there. There is some potential risk with folder based sub sites because cookies are per domain not per folder and if someone in a folder sub site adds malicious javascript he can potentially steal cookies from any of the sites if the user visits his sub site.

You can create a sub tree within a site that a user can edit as bprado is talking about doing and you can give a user a folder sub site and it will be fine if they are trusted users but if you are letting anyone sign up then you need much more control over what they can and can't do and you don't want them to have the power provided in the mojoPortal content features because as I said these features allow the user to do things that could be bad in order to allow them to also do cool good things by letting them put javascript in the page.

mojoPortal is not a framework for building social networking sites, the security issues in a social networking site are much different and that is not currently a goal for the project. mojoPortal aims to provide what is needed for a business web site with social features to leverage other social networking sites for promotion but not to build the next facebook.

Best,

Joe

bprado,

I wonder do you really want the content of 1000 churches all in one site or do you want to create a site for each church?

If you create a folder sub site for each church then you don't need 1000 roles in one site, you just make the appropriate person content administrator in his own site and then at least you don't have to customize mojoportal core because you still use roles to control who can edit.

I guess you would have some lookup list in the OnRegister event to check if the user registering is on the list of approved to have their own site and if the site is not already created. This way you don't do anything when other users register.

Best,

Joe

Hi,

It sounds like you have <add key="UseRelatedSiteMode" value="true" /> which makes it share users and roles across all sites. You can either set that to false and then the sites will have independent users and roles and therefore Content Administrators from one site are not also Content Administrators in the other sites. Or, if you do want to share users and roles across sites then you would need to make a role per site and set it as the siteSettings.SiteEditorRoles on each site to enable different editors in each site without making them Content Administrators. With related sites mode enabled then anyone in the Admins Role or Content Admintratorss role can edit anything in any of the sites but users in roles created and attached as SiteEditorRoles can only edit within the specific site.

Hope it helps,

Joe