On Wed, 2005-12-07 at 13:04 -0800, Brock Bland wrote:
> I have a couple of use cases that I was hoping this group could help me
> with.  
> 
> 1. I have a system with several roles defined and obviously users
> assigned to those roles.  When a user, say Bob who is in role1, logs in
> I need to find pages from paths in the following order.
> pages/_user/Bob
> pages/_role/role1
> pages
> 
> Is there a profiling rule that does this already?  If not what criteria
> do I need to add to a new one to get it to work?

You can either use two profiling rules... such as 'j2' and
'roll_fallback', or you can define a custom profiling rule. Take a look
in the /etc/sql/populate-db-default.sql for ideas.

> 
> 2. Say Bob is looking at a page that came from pages/_role/role1.  He
> wants to change it, but the change should be made on a user basis so a
> copy is made in pages/_user/Bob and Bob edits his personal copy.
> 
> Is this possible, and if so how do I set it up?

You have the right idea. However, AFAIK there is no automated copy from
the /_role/role1 to /_user/Bob upon customization. There is plenty of
work going on related to customization and site management... so please
submit a JIRA request if this feature is important enough to you.
 
> 
> Also, when a new user is created and assigned to a role and given a
> profiling rule a user directory is created for him.  What determines
> what all goes in this directory?  Is it just a default-page.psml file
> and a folder.metadata file to restrict access to this user?

It is copied from a special user home directory for the user 'template'.
You can customize the template, (/_user/template), as needed. Ownership
is configured for the new user.

> 
> I've read the design doc on this stuff but if it's in there I guess it's
> just not sinking in.  If anyone can provide a little insight for me I'd
> greatly appreciate.
> 

HTH,

Randy

> 
> Brock Bland
> 
> **********************************************************************
> This email and any files transmitted with it are confidential and intended 
> solely for the use of the individual or entity to whom they are addressed. 
> Any unauthorized review, use, disclosure or distribution is prohibited. If 
> you are not the intended recipient, please contact the sender by reply e-mail 
> and destroy all copies of the original message.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to