Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Controlling Personalization Scope

  Asked By: Chaim    Date: Nov 07    Category: MOSS    Views: 1026

I have been working with a client to develop web parts that support customization (shared scope) and personalization (user scope) and have been unable to get the expected behavior.

Depending on which page I add a web part to I get different behavior from the same Web Part. To try to troubleshoot this I have created a web part that displays the properties of WebPartManager.Personalization. It appears that all members have the right to enter shared scope on most pages and start in shared scope by default. The method toggle scope appears to have no effect under any circumstance however I have been able to toggle the scope through the query string in the form of

http://webparts/default.aspx?PageView=user

http://webparts/default.aspx?PageView=shared

If anyone can explain this behavior to me or point me to some documentation on how personalization is different in WSS3 / MOSS 2007 from ASP.NET 2 I would appreciate it as thus far I have not been able to find much information on this topic and the SDK has been of very limited use.

Share: 

 

1 Answer Found

 
Answer #1    Answered By: Donta Kirkland     Answered On: Nov 07

Personalization was broken in B1TR, B2, and B2TR. I bugged it each time
and it seems to be fixed in RTW.

Can you provide the code you are using so we can try an recreate the
problem?

 
Didn't find what you were looking for? Find more on Controlling Personalization Scope Or get search suggestion and latest updates.