pls HELP: webpart acting as shared but should be user (spellchecked)

3 May 2006 9:14 PM

arthernan

I have an almost finished page that uses webparts. And this is the
expected functionality. A logged on user hits a button and the button
opens a WebPart. Then the user logs off, next time he logs on he will
find the webpart already open. Now, if a different user logs on, the
fact that another user might have opened a webpart should not affect
the page. For him the page should only show webparts that were open
inside his session.
This is not what is happening right now. Currently, if a user opens a
webpart, and then a different user logs on, the newly logged user will
have whatever webparts that he might have opened in the past plus the
ones opened by other user. Almost like the webpage was being modified
by everybody.

I am creating the WebParts dynamically from user controls using the
LoadControl command; then I use the WebPartManager.CreateWebPart and
last WebPartManager.AddebPart.

I have looked at my config file and the code and everything looks fine.
When I steep through the code after the webpart has been created I can
see this variables.
WebPartManager1.Personalization.HasPersonalizationState equals True
WebPartManager1.Personalization.Scope is user
WebPartManager1.Personalization.Enabled equals True

Does anybody know what I am doing wrong? Do I need to save the state?

Arturo Hernandez

4 May 2006 3:58 AM

Engelbert

The WSS newsgroup you have posted (twice) to is the one dealing with admin
issues.

You'd be better posting this question about a web part you've written
yourself to the subnewsgroup for WSS programming issues which is

microsoft.public.sharepoint.windowsservices.development

where there are people who are more likely to be able to help you than in
this main newsgroup.

Engelbert

Show quoteHide quote

"arthernan" <arther***@hotmail.com> wrote in message
news:1146690860.908667.183690@e56g2000cwe.googlegroups.com...
>I have an almost finished page that uses webparts. And this is the
> expected functionality. A logged on user hits a button and the button
> opens a WebPart. Then the user logs off, next time he logs on he will
> find the webpart already open. Now, if a different user logs on, the
> fact that another user might have opened a webpart should not affect
> the page. For him the page should only show webparts that were open
> inside his session.
> This is not what is happening right now. Currently, if a user opens a
> webpart, and then a different user logs on, the newly logged user will
> have whatever webparts that he might have opened in the past plus the
> ones opened by other user. Almost like the webpage was being modified
> by everybody.
>
> I am creating the WebParts dynamically from user controls using the
> LoadControl command; then I use the WebPartManager.CreateWebPart and
> last WebPartManager.AddebPart.
>
> I have looked at my config file and the code and everything looks fine.
> When I steep through the code after the webpart has been created I can
> see this variables.
> WebPartManager1.Personalization.HasPersonalizationState equals True
> WebPartManager1.Personalization.Scope is user
> WebPartManager1.Personalization.Enabled equals True
>
> Does anybody know what I am doing wrong? Do I need to save the state?
>
>
> Arturo Hernandez
>