Thanks for your suggestions, see my comments below.
Do you still want users to override these default prefs, or strictly
the "old way"?
No, I don't think I would need strictly the old way. Users could be able
to override the default prefs if they have permission for the edit mode.
If you want the old way,
what about if I changed the PortletEntityImpl.getPreferenceSet to use
a conditional configuration:
if (PREFS_PER_USER)
prefNodePath =
MutablePortletEntity.PORTLET_ENTITY_ROOT + "/" + getId() +"/"+
principal.getName() +"/"
+ PrefsPreference.PORTLET_PREFERENCES_ROOT;
else
prefNodePath =
MutablePortletEntity.PORTLET_ENTITY_ROOT + "/" + getId() +"/"+
NO_PRINCIPAL +"/"
+ PrefsPreference.PORTLET_PREFERENCES_ROOT;
Otherwise, if you want default preferences in a special
"DEFAULTS_MODE" (which I think is a good use case)
then I don't think we can get that into the customizer in this short
notice
Mhm, I also think that a DEFAULTS_MODE would be a too heavy solution for
that and above all would require adaptations for all portlets.
We are running out of time on the 2.1 release
Its not even clear to me how this would work, or how the system would
know that its in "defaults mode"
Don't wanted to stress you with that before the 2.1 release ;)
This really has time. I just saw your post regarding the prefs merging
feature which didn't work for me.
So I think it's the best when I log a jira issue about that for now. Let
me further investigate in the prefs merging feature or the conditional
configuration of PortletEntityImpl.getPreferenceSet and I'll see whether
I find a solution that fits my use case.
Regards, Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
