The latest version of Dynamic User Directory supports a new token called [UserImage] and we wanted to highlight the current functionality of this feature and how we will be adding future enhancements to support even more options within the module.
History
First - A small history lesson. Before DotNetNuke has their own Image profile field type Dynamic Registration and Dynamic User Directory have supported user images already... The file is saved (typically to the DynamicRegistration_Images directory) under the portals root directory. For example \portals\0\dynamicregistration_images. The name of the file is then saved / mapped to a DNN core profile field and you could include an image directly in the HTML template of the user directory template. This is the "old school" way of handling user images and this will still work, you can actually review how this is handled at
http://dynregdemo.datasprings.com.
This process and how to get the images to show up is also explained in this forum post:
http://www.datasprings.com/dnn-modules/dynamic-user-directory/displaying-an-image-in-the-user-directory/
The method above (although the "old school" way) actually offers the most flexibility because you could setup a hyperlink to the main image, make the image src tag the thumbnail image etc...
New Functionality
Starting with the latest 4.0 release of Dynamic User Directory new features were added in place to build a more dynamic image token. The settings are defined under the control panel, within the module configuration area. Lets cover the configuration options there.
- Integration Type - This setting should be set to either DotNetNuke or Dynamic Registration. The DotNetNuke Integration type is used only if you are not saving the users image within Dynamic Registration. Basically the new DotNetNuke User Image profile type saves the fileID (a number) that references the files table. Dynamic Registration currently only offers the ability to store the filename or the full path and name to the file. So, for now, choose DotNetNuke if you are using their profile image field during registration, or choose Dynamic Registration if you are using that module.
- User Image Field - This setting should reflect the user image profile field that you are using within the DotNetNuke Core Profile fields. This setting should either be the image field (if you are using DotNetNuke Integration setting above) or a textbox profiled field where you have chosen to 'Map' your Dynamic Registration field to. Even if you are using Dynamic Registration for the users profile image, you still need to make sure and map this field to the DNN Core just like other Dynamic Registration fields.
- User Image Location - This is important because its typically a prefix to the users folder. Typically this is /portals/0/ if you are using the DotNetNuke integration, otherwise its typically /portals/0/dynamicregistration_images/ if you are using Dynamic Registration.
- Image Type - This setting reflects if you would like to display a thumbnail of the users image, a thumbnail with a link to the main user image, or simply their full image.
Optional Parameters:
- Enable jQuery Lytebox Effect?: - This setting will enable a jQuery Lytebox affect. The Lytebox effect is used when you are displaying a thumbnail with a full image. When the setting is enabled the full image will pop up with a nice Lytebox window rather then simply opening up in a new browser window.
- Thumbnail Prefix - Generally this should be "thumb_" if you are using Dynamic Registration and blank if you are using the DotNetNuke integration option. This prefix will be added to the filename/url for the thumbnail.
- Thumbnail Image Height / Width - This setting reflects the height and width of the thumbnail image.
- Alternate Thumbnail Image - This setting will showcase a thumbnail image if the users thumbnail image is empty. So, if the user doesn't have a profile image then instead of showing a blank or default image you can select the image you would like to be used here.
- User Online / Offline Image - These images are not really related to the users profile image but do reflect the [useronline] token within the template. These tokens will show a specific image if the user is online or offline (for example maybe a green dot or maybe a "I am online!" image when the user searches the directory.
Future Updates
The next version of Dynamic Registration will support more integration with the DNN Core profile property image type. So, in the future, you will have the option within Dynamic Registration to select to store the users image in the same method that the DotNetNuke Core saves the profile property which is stored as the fileID number instead of the filename.
I believe Don will be working on some videos shortly that highlight setting up and using the [UserImage] token so stay tuned!
Questions? Comments? Let us know!