Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Possible invalid Token Possible invalid Token
Previous
 
Next
New Post
6/17/2007 12:10 PM
 

in a new host user notification email that was sent to my mail box, the following token was not replaced

[Profile:FullName]

Is this a valid Token name? is it mis-spelled or something?

Thanks

Mark

 
New Post
6/17/2007 12:56 PM
 

there is an issue in DotNetNuke versions 4.5.2 to 4.5.3 with replacement of [profile:...] tokens that shall be solved in version 4.5.4


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
6/26/2007 9:55 AM
 

Hi Sebastian,

Just came across this issue when a new user registered on my site.... Is there a work around, or is it simply a case of waiting for 4.5.4?

Also, I noticed that if you have a custom property with a space in it, it causes an error - Char 62, Expected ';'. I'll post to Gemini.

Cheers
Roger

var dnn_ctr_ManageUsers_Profile_ProfileProperties_ctl07_Date of Birth_Req = document.all ? document.all["dnn_ctr_ManageUsers_Profile_ProfileProperties_ctl07_Date of Birth_Req"] : document.getElementById("dnn_ctr_ManageUsers_Profile_ProfileProperties_ctl07_Date of Birth_Req");
dnn_ctr_ManageUsers_Profile_ProfileProperties_ctl07_Date of Birth_Req.controltovalidate = "dnn_ctr_ManageUsers_Profile_ProfileProperties_ctl07_Date of Birth";
dnn_ctr_ManageUsers_Profile_ProfileProperties_ctl07_Date of Birth_Req.errormessage = "Date of Birth is Required";
dnn_ctr_ManageUsers_Profile_ProfileProperties_ctl07_Date of Birth_Req.display = "Dynamic";
dnn_ctr_ManageUsers_Profile_ProfileProperties_ctl07_Date of Birth_Req.evaluationfunction = "RequiredFieldValidatorEvaluateIsValid";
dnn_ctr_ManageUsers_Profile_ProfileProperties_ctl07_Date of Birth_Req.initialvalue = "";


DNN MVP
Events - Get the latest version - Upgrade now!!
Feedback 6.4.2 - Now available - Give it a go!
Find us on Codeplex - DNN Events, DNN Feedback
Requirements/Bugs - Please submit them on Codeplex
 
New Post
6/26/2007 1:13 PM
 

I blogged a workaround (see http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/1448/Default.aspx) for the notification issue, regarding blanks in the name it might be easier to create the property without speccial characters in the name and add the final version an English localization.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
6/26/2007 4:22 PM
 

Sebastian, Thanks for the info.

Looks like someone already fixed the blanks issue - http://support.dotnetnuke.com/issue/ViewIssue.aspx?p=0&id=5754 - meant to be in 4.5.4

I think your workaround only works for a few items, since I want to replace custom property tokens, I think I need [Profile:xxxx] and this isn't working currently. So I'll await 4.5.4 for the fix.

Thanks

Roger


DNN MVP
Events - Get the latest version - Upgrade now!!
Feedback 6.4.2 - Now available - Give it a go!
Find us on Codeplex - DNN Events, DNN Feedback
Requirements/Bugs - Please submit them on Codeplex
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Possible invalid Token Possible invalid Token


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out