Thank you Ralph for your answer.
They are really global like you will see in the code in
sthProfileManager (I have not the source code at the time I'm writing
this email). The pipelines are not used for base data and data.
I think it's a missing feature. I will have a look in the next days to
provide a patch to be able to have the behaviour I'm looking for.
Jean-Christophe
Ralph Goers a écrit :
CopletData is just the basic definition of a coplet. It is just a basic
shell for a coplet so it wouldn't really make sense to have it be
role/user based. And yes, this is the same for 2.2. The way I have
also understood this to work is that for personalization the user picks
fom the available coplet instances and modifies his layout.
However, I don't believe these aren't really "global". When you look at
the portal configuration you will notice that the copletbasedata,
copletdata, copletinstancedata and layouts are all retrieved via
pipelines. You should be able to make these pipelines behave
differently for different users.
HTH,
Ralph
Jean-Christophe Kermagoret wrote:
Hello,
I discovered copletdata and copletbasedata are both global. I agree
for copletbasedata, but why this behaviour for copletdata ? Is it the
same in the 2.2 portal ?
It seems to me it should be a good idea to permit a copletdata by role
or user to allow personalization by the user. That way, he could only
pick what is available in its copletdata profile and create
copletinstancedata based on these copletdata types.
Jean-Christophe
--
Jean-Christophe Kermagoret
[EMAIL PROTECTED]
