|Number of votes:||0|
It started out as a simple Dynamic Content element which displayed the name of the user viewing the page, to enable editors to add greetings like “Hello [user name], welcome to the page!”. I then realized there may be many other uses for that type of personalized Dynamic Content.
Using my own implementation of Anders Hattestad’s Dynamic Content base class (see this blog entry) I created an interface, a custom edit control and a few simple implementations of the interface that output basic user information. The implementation of the rendering class, however, will find all implementations of the interface in any of the application bin folder’s dlls using reflection.
Here's an example of how it might look (I tried to insert screen dumps here but EPiServer World does not seem to support it):
This personal information, like your users first name in the headline and your email address email@example.com are displayed by the ProfileInfo Dynamic Content. It can also display information about other users, like the user with username sogeti whose title is not set.
And in edit mode:
This personal information, like your users first name in the headline and your email address [DynamicContent:ProfileInfo]are displayed by the ProfileInfo Dynamic Content. It can also display information about other users, like the user with username [DynamicContent:ProfileInfo]whose title is [DynamicContent:ProfileInfo].
Each “instance” can be configured to display information either about a specific user or the user viewing the page. Based on the interface implementations available the editor can choose one to display, and a fallback, should the first one return empty (a property not set, user is anonymous etc.). The fallback may be another interface implementation or a free text string, as in the example “not set” above. For an anonymous user the same message, in this case, looks like this:
This personal information, like your users first name in the headline and your email address Email not set are displayed by the ProfileInfo Dynamic Content. It can also display information about other users, like the user with username sogeti whose title is not set.
The interface also includes a way to replace an existing implementation with a new one if, say, you would want the username to output backwards or rendered as an image instead. The class generating the email link (“-“ for the anonymous user is the fallback text) is actually a replacement implementation which inherits from the original Email implementation and replaces it:
And strictly there is no limitation to just the profile properties of the user. Using the information in the PageBase and EPiServerProfile objects fed to the interface it’s possible to output the user’s community mypage portrait or a message-of-the-day stored in a dynamic property.
The source code is available here. A short explanation of the files:
DynamicContentBase.cs: Base class for dynamic content, as mentioned in the beginning of this post.
IProfileProperty.cs: Interface that has to be implemented by classes rendering information in the ProfileInfo Dynamic Content.
ProfileInfo.cs: The actual Dynamic Content implementation. Calls all available IProfileProperty implementations at render time and in edit mode to populate the drop down lists of the dialog.
ProfileInfoFactory.cs: Singleton class that is responsible for finding IProfileProperty implementations at applicaiton start and sorting out replacements.
DefaultImplementaions.cs: Contains a base class for outputing simple string properties of the user profile, as well as several implementations for standard properties such as UserName, FirstName, LastName etc.
EmailAsLink.cs: Replaces the Email implementation in DefaultImplementations.cs, outputing a mailto link instead of just the email text.
And remember: You still have to add the Dynamic Content class ProfileInfo to the episerver/dynamicContent section of your web config file.