I've been wondering the same so took a look at the token replacement code in the GetSystemMessage of the Localization class.  Look like  [Custom:key] where key is the name of the custom profile property should do it.  I'll give it a try as soon as I get a chance.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

Hello Bill and Lee,

Did you manage to find a solution? :)

---

DotNetNuke Newbie!

I finally had time tonight to step through the code for both the shared methods Localization.GetSystemMessage and Localization.PersonalizeSystemMessage. Although it is possible to use the token [Profile:Key] when "Key" is one of the built-in profile properties, there is no provision in the existing code to replace tokens of the form [Profile: Key] or [ProfileProperties: Key] or [ProfileProperties: N] where "Key" is the name of or "N" is the index of a custom profile property.

Property information and values for custom profile properties are available in the ProfileProperties collection (of type ProfilePropertyDefinitionCollection) of the UserInfo.Profile object, but they are not being accessed.  It would be a relatively simple modification of the Localization.PersonalizeSystemMessage method to implement this. Guess we'll have to either make a core modification (which I don't recommend) or wait until this is implemented.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner