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 "David Sean Taylor (JIRA)" <je...@portals.apache.org> on 2005/12/16 21:25:47 UTC

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

User Specific Preferences 
--------------------------

         Key: JS2-449
         URL: http://issues.apache.org/jira/browse/JS2-449
     Project: Jetspeed 2
        Type: Improvement
  Components: Portlet Registry  
    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


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

Posted by Aaron Evans <aa...@gmail.com>.
David,
The testing I have done so far has worked perfectly.  Here's the
scenarios I've tested so far:

For a given portlet X, a preference, 'pref1', is configured in
portlet.xml with value 'initValue'.

There are two instances of portlet X, one in one page in frag ID A and
another in another page in frag ID B.  *No values for 'pref1' are
configured in the PSML.*

1. User 1 logs in and browses to the page containing frag ID A and
then goes into the edit portlet mode.  As expected, 'pref1' is set to
'initValue'.
2. User 1 changes the value to 'user1ValA' and saves his preferences
(in processAction, prefs.store() is called).
3. User 1 logs out and logs back in.  Browsing to frag ID A, as
expected, the pref is still set  to the new value, 'user1ValA'.
Browsing to frag ID B, as expected, the pref is still set to the
default 'initValue'.

4. User 2 logs in and browses to frag ID A, as expected, the pref
value is the initial value 'initValue'.
5. User 2 edits the preference and sets the value to 'user2ValA' and
saves his preferences.
6. User 1 logs out and logs back in and browses to frag ID A.  His
value for 'pref1' remains 'user1ValA' (as expected).

7. User 1 resets his preference and saves it (via prefs.reset('pref1')
then prefs.store() in processAction).   As expected,  his value is
saved as 'initValue' and the value for User 2 remains unchanged.

As stated above, values for the preference have not been specified in
the PSML fragments, so the User->PSML->portlet.xml chain has so far
not been tested.  This only tested the User->portlet.xml chain and
that preferences are indeed stored on a user by user basis.

So then I added PSML configured preferences (which I thought wouldn't
work properly, but they seemed to):

For a given portlet X, a preference, 'pref1', is configured in
portlet.xml with value 'initValue'.

There are *three* instances of portlet X, frag ID A, frag ID B and
frag ID C.   For frag ID A, no value for the preference was specified.
 For frag ID B, a value of 'psmlValB' was specified.  For frag ID C, a
value of 'psmlValC' was specified.

After resetting the prefs for User 1 and User 2:

1. User 1 logs in and browses to each PSML fragment.  As expected (and
as before), frag ID A used the portlet.xml value of 'initValue'.
However, frag ID B and C both used the PSML override values of
'psmlValB' and 'psmlValC' respectively.

2. User 1 updates his values for the preference to 'user1ValA',
'user1ValB' and 'user1ValC' with respect to frag IDs A, B and C.

3. User 2 logs in and the values for the preference are unaffected by
user 1 and default to the values as expected.

4. User 1 resets his value for the preference for frag A and the value
falls back to the value in portlet.xml (as expected since no value is
specified in the PSML).

5. User 1 resets his value for the pref for frag B and it falls back
to the value specified in the PSML as expected (IMO).

So it looks good as far as I can tell.  As I said, I thought there was
still a problem with PSML prefs, but in the way that I feel it should
work, it seemed fine.

Nice work!

-aaron


On 8/23/06, Aaron Evans <aa...@gmail.com> wrote:
> Thanks.
>
> I'll try to test this over the next couple of nights or this weekend.
> Hopefully my wife doesn't go into labour before then.  :)  I'll let
> you know what I find.
>
> On 8/23/06, David Sean Taylor (JIRA) <je...@portals.apache.org> wrote:
> >     [ http://issues.apache.org/jira/browse/JS2-449?page=comments#action_12430047 ]
> >
> > David Sean Taylor commented on JS2-449:
> > ---------------------------------------
> >
> > Aaron,  Ive checked in the initial implementation. Please test when you get a chance.
> > Note that  if you test with the Pick A Number portlet, it is using the session to cache prefs,
> > so its not a good test of prefs, because of that other problem we discussed with session termination.
> > Please let us know how your testing went...
> >
> > > 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


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

Posted by Aaron Evans <aa...@gmail.com>.
Thanks.

I'll try to test this over the next couple of nights or this weekend.
Hopefully my wife doesn't go into labour before then.  :)  I'll let
you know what I find.

On 8/23/06, David Sean Taylor (JIRA) <je...@portals.apache.org> wrote:
>     [ http://issues.apache.org/jira/browse/JS2-449?page=comments#action_12430047 ]
>
> David Sean Taylor commented on JS2-449:
> ---------------------------------------
>
> Aaron,  Ive checked in the initial implementation. Please test when you get a chance.
> Note that  if you test with the Pick A Number portlet, it is using the session to cache prefs,
> so its not a good test of prefs, because of that other problem we discussed with session termination.
> Please let us know how your testing went...
>
> > 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


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

Posted by Aaron Evans <aa...@gmail.com>.
When I tested it, I was quite pleased with it.

Thanks. :)

-aaron

On 12/8/06, David Sean Taylor (JIRA) <je...@portals.apache.org> wrote:
>      [ http://issues.apache.org/jira/browse/JS2-449?page=all ]
>
> David Sean Taylor resolved JS2-449.
> -----------------------------------
>
>     Resolution: Fixed
>
> seems to be working for a while now
>
> > 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


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

Posted by Aaron Evans <aa...@gmail.com>.
Hey, no problem!  I just wanted to make sure it was indeed pegged for 2.1

thx!

On 5/18/06, David Sean Taylor (JIRA) <je...@portals.apache.org> wrote:
>     [ http://issues.apache.org/jira/browse/JS2-449?page=comments#action_12412355 ]
>
> David Sean Taylor commented on JS2-449:
> ---------------------------------------
>
> Aaron, I haven't forgotten. Im involved in another project here.
> Behind schedule, usual. I will get this in for 2.1 release, just later than expected. My apologies for any inconvenience this has caused you.
>
> > User Specific Preferences
> > -------------------------
> >
> >          Key: JS2-449
> >          URL: http://issues.apache.org/jira/browse/JS2-449
> >      Project: Jetspeed 2
> >         Type: Improvement
>
> >   Components: Portlet Registry
> >     Versions: 2.1-dev
> >     Reporter: David Sean Taylor
> >     Assignee: 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


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

Posted by "David Sean Taylor (JIRA)" <je...@portals.apache.org>.
    [ http://issues.apache.org/jira/browse/JS2-449?page=comments#action_12430047 ] 
            
David Sean Taylor commented on JS2-449:
---------------------------------------

Aaron,  Ive checked in the initial implementation. Please test when you get a chance.
Note that  if you test with the Pick A Number portlet, it is using the session to cache prefs, 
so its not a good test of prefs, because of that other problem we discussed with session termination.
Please let us know how your testing went...

> 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


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

Posted by "David Sean Taylor (JIRA)" <je...@portals.apache.org>.
    [ http://issues.apache.org/jira/browse/JS2-449?page=comments#action_12369711 ] 

David Sean Taylor commented on JS2-449:
---------------------------------------

>From Aaron Evans:

 Portlet Preferences are not stored on a user by user basis.

Looking in the database, it looks as though the preferences are being associated with the fragment ID for the portlet of the psml page.

I am pretty sure that the intention of the portlet spec is to enable the storing of preferences on a user by user basis. But apparently this is not possible in jetspeed unless the user creates a new portal page?

The data I see in the DB seems to support this:

I login as user A, and I have a portlet preference for one of my report portlets called reportTimeZone. By default is set to US/Eastern.

User A edits his portlet preferences and sets the reportTimeZone to be US/Pacific.

Looking in the prefs_property_value table, can see the newly created value. It has node ID 2875 and value US/Pacific. The property name is 0, I assume that this is the index in the array if it were multi-valued.

I then look in the prefs_node table for a row with node_id=2875. The row is present and the full path of the node is:

 /portlet_entity/reports-3/no-principal/preferences/reportTimeZone/values

Note that reports-3 is the fragment ID for the portlet fragment in the psml page.

However, instead of 'no-principal', I would have expected to see the user name of user A.

So now I log in as user B and go to edit my portlet preferences and the value of the reportTimeZone preference is set to US/Pacific, not the default US/Eastern I would have expected.

So I then, as user B, set the reportTimeZone to US/Central and update my preferences.

Sure enough, it overwrites the value in the prefs_property_value table to US/Central.

So, in order to get the behaviour I need, I would have to generate portal pages for each user and vary the id of the portlet fragment? This does not seem like a good solution to me.

Further, in my environment, users are not permitted to create their own pages and customize them. I am simply providing a form in the doEdit method of my portlet to allow users to customize the behaviour of the portlet.

So, in my environment, imagine I had a weather portlet on a portal page. If someone sets their preferred city to be Bangkok, then *all* users will get weather for Bangkok!

This does not seem right to me...

> User Specific Preferences
> -------------------------
>
>          Key: JS2-449
>          URL: http://issues.apache.org/jira/browse/JS2-449
>      Project: Jetspeed 2
>         Type: Improvement
>   Components: Portlet Registry
>     Versions: 2.1-dev
>     Reporter: David Sean Taylor
>     Assignee: 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


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

Posted by "Terry Partridge (JIRA)" <je...@portals.apache.org>.
    [ http://issues.apache.org/jira/browse/JS2-449?page=comments#action_12377882 ] 

Terry Partridge commented on JS2-449:
-------------------------------------

Yes, I also have a need to store user specific preferences without having to generate portal pages for each user. 

> User Specific Preferences
> -------------------------
>
>          Key: JS2-449
>          URL: http://issues.apache.org/jira/browse/JS2-449
>      Project: Jetspeed 2
>         Type: Improvement

>   Components: Portlet Registry
>     Versions: 2.1-dev
>     Reporter: David Sean Taylor
>     Assignee: 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


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

Posted by "David Sean Taylor (JIRA)" <je...@portals.apache.org>.
    [ http://issues.apache.org/jira/browse/JS2-449?page=comments#action_12412355 ] 

David Sean Taylor commented on JS2-449:
---------------------------------------

Aaron, I haven't forgotten. Im involved in another project here.
Behind schedule, usual. I will get this in for 2.1 release, just later than expected. My apologies for any inconvenience this has caused you.

> User Specific Preferences
> -------------------------
>
>          Key: JS2-449
>          URL: http://issues.apache.org/jira/browse/JS2-449
>      Project: Jetspeed 2
>         Type: Improvement

>   Components: Portlet Registry
>     Versions: 2.1-dev
>     Reporter: David Sean Taylor
>     Assignee: 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


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

Posted by "Aaron Evans (JIRA)" <je...@portals.apache.org>.
    [ http://issues.apache.org/jira/browse/JS2-449?page=comments#action_12412345 ] 

Aaron Evans commented on JS2-449:
---------------------------------

Hey guys,
Just wondering if this will make it into 2.1.  I am *really* hoping it does.  I have been running in production on 2.0 for a while now and have been waiting for 2.1 to upgrade, but this is one of my big requirements.

cheers,
aaron

> User Specific Preferences
> -------------------------
>
>          Key: JS2-449
>          URL: http://issues.apache.org/jira/browse/JS2-449
>      Project: Jetspeed 2
>         Type: Improvement

>   Components: Portlet Registry
>     Versions: 2.1-dev
>     Reporter: David Sean Taylor
>     Assignee: 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


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

Posted by "Thorsten Berger (JIRA)" <je...@portals.apache.org>.
    [ 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


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

Posted by "David Sean Taylor (JIRA)" <je...@portals.apache.org>.
     [ http://issues.apache.org/jira/browse/JS2-449?page=all ]

David Sean Taylor resolved JS2-449.
-----------------------------------

    Resolution: Fixed

seems to be working for a while now

> 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