profile based website / portal

[christian bindeballe <ot...@gmail.com>]

hello everyone,

has somebody experience with a cocoon portal that serves different pages 
according to the profile (role / username) of a user?

if so, is it sufficient to have

a) the global profile in copletdata and copletinstancedata and
b) identical profile-files for each role/username which also have 
additional coplets which are only for the actual user/role

or do you have to have

a) a global profile and
b) in each other role/user-profile _only_ those coplets wich are to be 
served _only_ to those users?

also for a set-up like this, do you have to have all coplets configured 
with an authentication-handler?

i find the documentation concerning this very ambiguous.
any ideas or suggestions are highly appreciated.

best regards,

christian

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

Re: profile based website / portal

[christian bindeballe <ot...@gmail.com>]

2006/1/24, Ralph Goers <Ra...@dslextreme.com>:
> What Cocoon version?
>


I'm using version 2.1.8

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

Re: profile based website / portal

[Ralph Goers <Ra...@dslextreme.com>]

What Cocoon version?

christian bindeballe wrote:

> At the moment I have a global profile in each of those folders 
> (portal.xml) and also an additional portal-role-admin.xml. However, if 
> I log on with a user (e.g. the sample-portal user "cocoon") that has 
> admin privileges (it's role is admin), the profile loaded is always 
> the global one. The role of that user is defined in a file called 
> sunrise-user.xml. I know it is being used, since I defined a user 
> called abc which is also able to log on. But calling a role-dependent 
> profile doesn't seem to work. :(
> Any idea what could be wrong here?
>
> christian
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

Re: profile based website / portal

[christian bindeballe <ot...@gmail.com>]

Ralph Goers schrieb:
> These files are somewhat independent from each other.
> 

[...]
> 
> Ralph


Thanks Ralph!

At the moment I have a global profile in each of those folders 
(portal.xml) and also an additional portal-role-admin.xml. However, if I 
log on with a user (e.g. the sample-portal user "cocoon") that has admin 
privileges (it's role is admin), the profile loaded is always the global 
one. The role of that user is defined in a file called sunrise-user.xml. 
I know it is being used, since I defined a user called abc which is also 
able to log on. But calling a role-dependent profile doesn't seem to 
work. :(
Any idea what could be wrong here?

christian

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

Re: profile based website / portal

[Ralph Goers <Ra...@dslextreme.com>]

These files are somewhat independent from each other.

copletdata is global and defines all the portlets available to be used.

copletinstancedata defines all the portlet instances (You define multiple
instances of portlets defines in copletdata if you wish).  This can be a
default or particular to a role or user. The portlets referenced must be
defined in the copletdata.

layout defines the pages and where the portlet instances appear on them. 
The layout can be a default or particular to a user or role.  portlet
instances referenced in the layout must exist in the copletinstancedata.

If you have one copletinstancedata then, in theory, any user can access
any of the instances. However, that is actually hard to do unless the
user's layout refers to the instance.

In the end, how you manage these is really up to how you want your site to
behave.

Ralph

christian bindeballe said:
> hello everyone,
>
> has somebody experience with a cocoon portal that serves different pages
> according to the profile (role / username) of a user?
>
> if so, is it sufficient to have
>
> a) the global profile in copletdata and copletinstancedata and
> b) identical profile-files for each role/username which also have
> additional coplets which are only for the actual user/role
>
> or do you have to have
>
> a) a global profile and
> b) in each other role/user-profile _only_ those coplets wich are to be
> served _only_ to those users?
>
> also for a set-up like this, do you have to have all coplets configured
> with an authentication-handler?
>
> i find the documentation concerning this very ambiguous.
> any ideas or suggestions are highly appreciated.
>
> best regards,
>
> christian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org