You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Thorsten Berger (JIRA)" <je...@portals.apache.org> on 2006/12/11 18:44:26 UTC

[jira] Commented: (JS2-449) User Specific Preferences

    [ http://issues.apache.org/jira/browse/JS2-449?page=comments#action_12457424 ] 
            
Thorsten Berger commented on JS2-449:
-------------------------------------

I'm a bit wondering why switching back to the old behaviour isn't configurable. At least I haven't found it and please correct me if I'm wrong.

This seems to prevent one of my important use cases: the admin should be able to configure portlets on public portal pages.

E.g. imagine that admin wants to put the Google Maps portlet on the (publicly viewable) start page and sets another location in the prefs than the default one. This results in only admin seeing the correct location, non-logged-in guests still have San Francisco. The same for RSS portlets etc.

I tried to use the "mergeSharedPreferences" feature, but could not achieve this behavoiur. Furthermore there is always a preference node for the guest user created by just viewing the page and this overrides always the "no-principal" prefs (besides that one can't graphically edit "no-principal" prefs).
Using the Portlet Application Manager to set default prefs is insufficient too, as they're saved per portlet definition, not per entity.

Thanks in advance for any advice, Thorsten


> User Specific Preferences
> -------------------------
>
>                 Key: JS2-449
>                 URL: http://issues.apache.org/jira/browse/JS2-449
>             Project: Jetspeed 2
>          Issue Type: Improvement
>          Components: Portlet Registry
>    Affects Versions: 2.1-dev
>            Reporter: David Sean Taylor
>         Assigned To: David Sean Taylor
>             Fix For: 2.1-dev
>
>
> Preferences should be user-specific on all pages.
> If User A comes to page /roles/X/x.psml, and stores a pref P1 on portlet x1, and then User B comes to page /roles/X/x.psml, and also stores a pref P1 on portlet x1, the prefs for those two users should be different.
> I am considering making this feature optional, but the problem is that the semantics are intrinsic in the data model.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Re: [jira] Commented: (JS2-449) User Specific Preferences

Posted by Thorsten Berger <in...@thorsten-berger.net>.
Aaron Evans wrote:
> You could set the preferences in the PSML as read-only. That way, the
> user can't alter them and they will be identical for all users.
>
Unfortunately this is not graphically supported and would not be very
intuitive (possibly a bit confusing to administrative end-users).
> The old way just didn't make any sense.  In the old way, if user A
> changes a preference, it would then be changed for all users.
>
I know the old behaviour and I do think it made sense for at least the
use case mentioned. Our users have their own home folders and were
already able to save their portlet prefs this way.

Regards, Thorsten


> -aaron
>
> On 12/11/06, Thorsten Berger (JIRA) <je...@portals.apache.org> 
> wrote:
>>     [ 
>> http://issues.apache.org/jira/browse/JS2-449?page=comments#action_12457424 
>> ]
>>
>> Thorsten Berger commented on JS2-449:
>> -------------------------------------
>>
>> I'm a bit wondering why switching back to the old behaviour isn't 
>> configurable. At least I haven't found it and please correct me if 
>> I'm wrong.
>>
>> This seems to prevent one of my important use cases: the admin should 
>> be able to configure portlets on public portal pages.
>>
>> E.g. imagine that admin wants to put the Google Maps portlet on the 
>> (publicly viewable) start page and sets another location in the prefs 
>> than the default one. This results in only admin seeing the correct 
>> location, non-logged-in guests still have San Francisco. The same for 
>> RSS portlets etc.
>>
>> I tried to use the "mergeSharedPreferences" feature, but could not 
>> achieve this behavoiur. Furthermore there is always a preference node 
>> for the guest user created by just viewing the page and this 
>> overrides always the "no-principal" prefs (besides that one can't 
>> graphically edit "no-principal" prefs).
>> Using the Portlet Application Manager to set default prefs is 
>> insufficient too, as they're saved per portlet definition, not per 
>> entity.
>>
>> Thanks in advance for any advice, Thorsten
>>
>>
>> > User Specific Preferences
>> > -------------------------
>> >
>> >                 Key: JS2-449
>> >                 URL: http://issues.apache.org/jira/browse/JS2-449
>> >             Project: Jetspeed 2
>> >          Issue Type: Improvement
>> >          Components: Portlet Registry
>> >    Affects Versions: 2.1-dev
>> >            Reporter: David Sean Taylor
>> >         Assigned To: David Sean Taylor
>> >             Fix For: 2.1-dev
>> >
>> >
>> > Preferences should be user-specific on all pages.
>> > If User A comes to page /roles/X/x.psml, and stores a pref P1 on 
>> portlet x1, and then User B comes to page /roles/X/x.psml, and also 
>> stores a pref P1 on portlet x1, the prefs for those two users should 
>> be different.
>> > I am considering making this feature optional, but the problem is 
>> that the semantics are intrinsic in the data model.
>>
>> -- 
>> This message is automatically generated by JIRA.
>> -
>> If you think it was sent incorrectly contact one of the 
>> administrators: http://issues.apache.org/jira/secure/Administrators.jspa
>> -
>> For more information on JIRA, see: 
>> http://www.atlassian.com/software/jira
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
>> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Re: [jira] Commented: (JS2-449) User Specific Preferences

Posted by Aaron Evans <aa...@gmail.com>.
You could set the preferences in the PSML as read-only. That way, the
user can't alter them and they will be identical for all users.

The old way just didn't make any sense.  In the old way, if user A
changes a preference, it would then be changed for all users.

-aaron

On 12/11/06, Thorsten Berger (JIRA) <je...@portals.apache.org> wrote:
>     [ http://issues.apache.org/jira/browse/JS2-449?page=comments#action_12457424 ]
>
> Thorsten Berger commented on JS2-449:
> -------------------------------------
>
> I'm a bit wondering why switching back to the old behaviour isn't configurable. At least I haven't found it and please correct me if I'm wrong.
>
> This seems to prevent one of my important use cases: the admin should be able to configure portlets on public portal pages.
>
> E.g. imagine that admin wants to put the Google Maps portlet on the (publicly viewable) start page and sets another location in the prefs than the default one. This results in only admin seeing the correct location, non-logged-in guests still have San Francisco. The same for RSS portlets etc.
>
> I tried to use the "mergeSharedPreferences" feature, but could not achieve this behavoiur. Furthermore there is always a preference node for the guest user created by just viewing the page and this overrides always the "no-principal" prefs (besides that one can't graphically edit "no-principal" prefs).
> Using the Portlet Application Manager to set default prefs is insufficient too, as they're saved per portlet definition, not per entity.
>
> Thanks in advance for any advice, Thorsten
>
>
> > User Specific Preferences
> > -------------------------
> >
> >                 Key: JS2-449
> >                 URL: http://issues.apache.org/jira/browse/JS2-449
> >             Project: Jetspeed 2
> >          Issue Type: Improvement
> >          Components: Portlet Registry
> >    Affects Versions: 2.1-dev
> >            Reporter: David Sean Taylor
> >         Assigned To: David Sean Taylor
> >             Fix For: 2.1-dev
> >
> >
> > Preferences should be user-specific on all pages.
> > If User A comes to page /roles/X/x.psml, and stores a pref P1 on portlet x1, and then User B comes to page /roles/X/x.psml, and also stores a pref P1 on portlet x1, the prefs for those two users should be different.
> > I am considering making this feature optional, but the problem is that the semantics are intrinsic in the data model.
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org