I am curious if someone might know how to pull this off. I have user pages for my users and one of the things I will want to allow the user to do is have a "Bio" image display on the page. I would love it if it could be their DNN (profile) avatar image. That way I wouldn't have to use an HTML module and allow the user to upload lots of images and fill up our disk space. I was thinking I could even add it to the skin. Is their an easy way to access user profile images? Thanks and I hope that all makes sense.

[Profile: Photo] is the token for the current user's profile photo. You can use this anywhere that you can use replaceable tokens. You can use it in an HTML module to display the photo. To to this, you'll need to insert an img tag in the HTML or Source mode of the editor:

< img alt="" src="https://www.dnncreative.com/Portals/0/[PROFILE: PHOTO]" / >

If you leave off the "Portals/0/" part, the Rad editor will insert that proper portal code for you. I haven't tried this on a site that uses the FCK Editor, so the behavior may be slightly different. In my limited fiddling, it appears the [Portal: Photo] is replaced with a url that serves us the photo.


(You'll see where I've inserted some spaces in the above to make this display correctly ...)

Ohhh bless you Mr. Craig. I was hoping it was that easy. I probably should have looked through some of my DNN documentation, because my first guess was that it would be a token of some sort. I sure do love this site. I am very glad to pay for the membership!

I will have to play around. I don't want the current users profile. I want the image to be of the user who owns the page. Each user has his/her own page with his/her photo on it based on their profile image. I am sure it is still something along the lines of tokens.

Okay I can get the current user's photo to display just fine within the HTML Module. What I need to be able to do is display a particular users current profile photo. I could add an image and point directly to the user's photo, but if they change their profile photo, the image I place in the HTML Module won't be updated automatically to display the user's new profile image. I hope that makes sense.

I do not think that there is a token that will display an an arbitrary user's image, or other profile information.  You would have to write something like that yourself.

You can user UserInfo.GetProperty based on the UserId of the "page owner."  It would be fairly easy to create a simple module to display the image, or other property information.

If you aren't familiar with or put off by the notion of creating modules for DotNetNuke, Shaun Walker recently wrote a nice little blog post about a simple way of creating modules.  Of course, you will need to know a little bit about programming in a .NET language such as VB.

Just as an aside, how do you assign "page ownership" to a user? 

Right now we are just manually creating a page based on a template and giving the new user permissions to each module we want him/her to edit and not permission to the page. The reason we are doing this is so they can not create additional pages. As for creating a module, I just bought the DNN module programming book and would like to try. I have developed small asp.net (c#) web applications so it will be a learning curve for me. It will be fun, but I am sure I will end up doing it over many times before it is right. Thanks for the replies to my posts!

A couple of "starter" hints.

Take a look at Shaun's blog post.  The approach that he mentions cuts a lot of the "extra" stuff out of the process.  You can create a perfectly functional module with two or three files, depending on how you do it.

For starters, hard code the UserID so that you don't have to worry about settings or getting it from somewhere else.

Once you have a simple module version working, you might consider putting the UserID into a metatag that you can add to a page's Page Settings.

Finally, you can expand this to add module settings for specifying UserID or other variables.

If you do it that way, you'll maximize the use of your ASP.NET background, and not get bogged down with the full details of what is possible in the DotNetNuke framework.  It might help you get some of the mechanics into perspective.