That's the template I started with and stripped down to the bare minimum. I saw Jason Peterson's post earlier in this thread - /Community/Forums/tabid/68/aff/184/aft/49136/afv/topic/Default.aspx#60496 - which gave me the idea to try the AS CONTROL PROFILELINK token. I found that token mentioned in the Templates Tokens and Styles documentation but I can't find anything that looks like it will work to get the profile picture. The default tokens are rendering as text for me.

FWIW, the Inbox, Alert, and Login/Logout tokens seem to be working fine, except I don't now how to enable pop-up notifications, which is one of the main reasons I want to make the Welcome Center view part of my skin.

Never mind about the notifications. Those are working. User error on that one.

The image is generated by the active:ProfilePicture function, you will need to make sure you include all parts of that function. If you want to experiment, create a custom view, as it seems to render better than imbedding as a skin object (which still doesn't work for me).

I've been able to get everything I wanted in the Welcome Center to work using a custom view, but I really want to use it as a skin object because I want it on every page in my site and I don't want to have to deal with it as a module instance. I will keep experimenting and post on here if I find something that works.

Dan - can you please try my suggestion of just putting these tokens into your template and tell me if they are converted to values: I really don't see how it can work unless the template is converting these?

I put those tokens into my skin, and got this in the page: Is that what you are referring to?

[ AS:SOCIALUSER:USERID ] [ AS:SOCIALUSERISPLAYNAME ]  

Yes - my point is that this can not work if the active:socialwelcome server control is not converting these tokens into user values to feed into the ProfilePicture control. I really don't see how this could work? Perhaps Will or Ben could shed some light on it please?

I was just able to get working in my skin object what I needed to (user profile URL, user photo, firstname, displayname, and username) using these tokens:
[ AS : PROFILE : USERURL ]
[ DNN : PROFILE : ProfilePicture ]
[ DNN : PROFILE : FirstName ]
[ DNN : PROFILE : DISPLAYNAME ]
[ DNN : PROFILE : USERNAME ]

I attached a text file with the template I got to work in my Welcome Center skin object.

It would be handy if we had a definitive list of tokens that are certain to work in a skin object.

Nice job Ray. I was just going to post that you need to use "[DNN:PROFILE" in the skin object, You can also use the profile picture handler instead of the picture control. There is an example of how to use it in the Who's Online custom view.

Thanks, Will. Where can I find the Who's Online custom view?

In the custom view examples topic...
http://www.activemodules.com/Commun...fault.aspx

Thanks for the pointer.

Would there be any advantage (and would it work) to use [ AS : HANDLER : PROFILEPIC ] instead of [ DNN : PROFILE : ProfilePicture ] ?

The handler is faster and supports any image size you specify instead of using the values in the control panel.

Thanks for the insight, Wil. I modified my template to use the handler, now.

Do you know why the AS : PROFILE tokens aren't working in a skin object?

Yes. If we allowed you to use the AS:PROFILE tokens in the skin object then when you visited a user profile page other than your own the skin object would be parsed with the data from current profile. There are also a few other possibilities, but basically, it's setup this way to keep information as secure as possible.

Thanks Ray - that works for me.

Just a note - if you use the imagehandler from the Online view you need to change the [ AS:PROFILE:USERID ] token to: [DNN:PROFILE:USERID]

Yes, I had to change the AS to DNN for the userid, too, but forgot to note that in my post. Thanks for catching that.

Posted By Will M on 13 Mar 2010 10:59 PM
Yes. If we allowed you to use the AS:PROFILE tokens in the skin object then when you visited a user profile page other than your own the skin object would be parsed with the data from current profile. There are also a few other possibilities, but basically, it's setup this way to keep information as secure as possible.

I see, Will. I hadn't considered that. It totally makes sense, now. Thanks!