I recently updated a working installation of DNN 5.1 and DUD 2.5 to DNN 5.2.2 and DUD 3.0. After the upgrade, no users would appear in the directory. I traced the problem to changes in the Item / List Template and User Detail Template that need to be made to work in the new configuration.

In particular, it seems that some of the tokens are case-sensitive so tokens such as [FirstName] cause an error and must be changed to [firstname] for anything to be displayed. In addition, some tokens such as [MidddleName] and [Unit] are no longer supported and should be removed altogether.

I'm not sure if the HTML will come across, but here goes... So for example, I had to change:

[FirstName] [MiddleName] [LastName] [Suffix]

[Street] [Unit]

[City] [Region] [PostalCode]

[Email]

[Telephone]

[UserRoles]

View Details

---

 

to:

[firstname] [lastname]

[Street]

[City] [Region] [PostalCode]

[email]

[Telephone]

[UserRoles]

View Details

---

Yes, these properties are there in Manage Profile Properties. However, they are not used in my test set of users. If I change "[MiddleName]" to "[middlename]" in the template, then instead of being displayed as "[MiddleName]" it is displayed as "".

Actually, it seems even "[middlename]" in the template is displayed as "[middlename]" in the directory.

Thanks for explaining that. But just because a user hasn't entered data for a field yet shouldn't mean it can't be used in a template. What happens when the first user DOES enter their middle name or does add a unit number to their address? (That's a rhetorical question of course.)

It might be better for all unknown tokens to return "" instead of their name. Developers could be warned about Invalid tokens when *saving* a template but could accept this if they understand the implications.

Onward!