After I upgraded my site to 4.5.2 I have noticed that in the "User Registered" e-mail that is sent that the first and last names even if specified by the user are NOT transmitted in the e-mail.

I have not modified the text or anything on the e-mails.  Has anyone else noticed this?

In either DNN v 4.5.1 or 4.5.2 there were significant changes made to DotNetNuke.Services.Localization.TokenReplace, particularly in the area of defining the concept of and a property for the "AccessingUser" and which (if any) Profile properties the AccessingUser have sufficient access level permissions to view. In the replacedTokenValue function, a check is made on AccessingUser.UserId=Null.NullInteger.  If the AccessingUser is unauthenticated (UserID=-1), any attempt to replace tokens for Profile properties such as Firstname, Lastname, etc. return String.Empty rather than the property value.  It is in the shared function TokenReplace.Create that the AccessingUser first set from the HttpContext as follows: AccessingUser= CType(HttpContext.Current.Items("UserInfo"), DotNetNuke.Entities.Users.UserInfo). Unfortunately, in the case of a new user registering, his/her UserInfo object passed in the HttpContext is still the default for an unauthenticated user (with UserID=-1).  The correct UserInfo for the new registration is being passed to TokenReplace.Create, so the information is there, but not accessible to the "AccessingUser" even for tokenizing the body of the new registration e-mail being sent to the Administrator.  Either the HttpContext needs to be updated to pass the newly registered UserInfo object or the TokenReplace.Create and/or TokenReplace.replacedTokenValue methods will need modification to allow access to profile information that is being e-mailed to the Administrator.

I'll check Gemini and if it is not already reported, log the problem.

Is there any temporary workaround for this issue?