Email template editing problem
Good morning,
I am trying to personalize the email generated by the UE created template when a new user registration form is completed. I have edited the template created by UE to create 2 record sets and the fields entered in their respective places. I used the Random Password binding to generate a 10 digit validation code, I did not encrypt it. The end goal is to create a link to have the new user use for a confirmation that the email address is valid.
This sounds a lot to me like what the Security Assist Forgot password page does and if this is a more fitting plan with the Encrypted Password/Return behaviors, please advise where to find the instructions for use; I did not notice those areas in GSG. I have not spent a lot of time trying them. What I did not notice in my little bit of goofing around with them was the template file creation, its location, or how to modify it's contents and this was the main reason for not looking harder into this option. If Sec Assist 2 is the better option for this, I definitely like the thought of the encryption, I have seen it works fine on every email system I have tried and would like to pursue this avenue.
If the Sec Assist 2 option is not the way to go here, can you help me with the current issue:
The error that I am getting when I test the page refers to the Email template file blank5.php, lines 38 and 40, in the code, this is where the record sets are defined. When I tested page before the modification, email sent as expected. I did not want all form contents to include password being sent to new user.
My first question is: can I personalize the UE created templates with record sets?
My second question is: If I can do this, is there something that I am missing to create these record sets? The blank5 by itself file previews OK except for no data fields in it.
Both record sets in Blank5 are set to filter by session variable for each of the variables created in DA insert record behavior in the registration page; both are different because the serialization of the records in the 2 affected tables is different.
Both files are in the Archive.zip file attached.
