Once you store the prefs, they will go to the specific user and
override the old prefs
However, if you turn on merge, the window-specific (old-way) should
continue to display up until you save
At this point your user-specifc prefs will permanently override
Are you seeing different behavior?
David,
as far as I remember, I've not been able to achieve that behaviour. But
that's already about two months ago, so I'd have a look at this again if
the following isn't accurate (any more).
The former window-specific prefs of portlet entities have been stored
under a node with the name "no-principal" (e.g.
/portlet_entity/welcome-1/no-principal/preferences), right?
So I enabled the merging feature and set the "no-principal" prefs of the
portlet entity manually in the db.
The problem was, that always a preference node for the guest user (and
probably for all other users too) had been created by just viewing the
page. This has overridden my "no-principal" prefs.
But, as in my comment to JS2-449, I'd rather completely use the old
behaviour for the mentioned use case: a portal admin should be able to
put portlets on a public page and configure it for all users. Is that
still someway supported over the UI?
I mean if the above would work and an admin user could set the
"no-principal" prefs, that would probably be a solution.
Regards, Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
