Hello All,

I'll need a feature and was wondering if any one already did somehting like it.

What I need: Create a "default" page for every user after registration. Give the user permission to edit and create child pages. User will have this permissions only to his page and childs. I dont want to create a role for every user (will be too many).  

Where I'm heading: Use the RegistrationHandler to create the page. Build a custom table where I'll keep the user and his "default" page. Change the behavior of the authentication to allow users who "own" the page to edit and creat childs under it. 

Where I'm lost: Couldn't find a way to allow the user to edit his pages without messing in the mojoportal core. 

Maybe something like the "UserSignInHandler" ( "UserCanEditHandler" ) could allow me to implement the "custom rule". 

Any sugestions?

I just asked a similar question.  Hmmmm..... I mojoPortal is setup perfect, except I want a user to only be able see and access Documents he Owns.

I'm totally new to web administration.  I am not new to Windows Forms or services.  What I did was I created a Upload Web Service to handle large files that I can access with windows forms using MTOM.  I want MyService under my domain that mojo is under and I want to add a table in the SQL database to record files that are uploaded.  Reason being is that I want to upload files that have children files.

Hi Joe !!! 

Thanks for the answer !!!

Actually the users with that kind of permission will be secure and validated users. Imagine a site where "churchs" (example) can register and manage their pages. Only after documental comprovation they gain full access. And everyone else can register and have access to those pages (read only access). The problem is when we have thousands of "churchs" and can't manage thousands of roles.

Please let me know what you think of my plans:

- create a new table to keep track of "page owners" (could add a new field to mp_table but that would mess with the core and I'll try to avoid this).

- create a new table to "mark" a role as "user based". 

- create a Handler that can be customized to override the read of "CreateChildPageRoles" and "EditRoles" in PageSettings.cs. (here I'll need to merge 4 life :)

- Implement the Handler in a way that if a role is "user based" it will only be returned if SiteUser is the owner of the page. 

Just to clarify, I will prefer to use mojo for my biz site and most likely use it for a long time.  As far as my hair-brained ideas, I might have to venture out and even to a different host.

Something went wrong JOE. Could not set the role only for one subsite. Don't matter where I add the user to the role (in the main site or in the subsite) he get's content manager in all subsites (including the root site).

Maybe I'm not understanding how this work's ... Any clues?

EDIT: I found that even if I'm in a sub-site, mojoportal set's the role of the "root site" (siteid = 1) and not the "new one" (siteid = 3) created to the site. Maybe it's a bug? Any help would be appreciated ....