I have a child portal created from a template with four security roles defined in addition to the defaults roles. When I add one of the four roles the expiry date autofills to todays date. It does not occur when adding the standard roles. Also does not occur in the child from which the template was made for any of the roles. Am I missing some setting somewhere or something else? Anyone have ideas or suggestions? Thanks.

Recently uped level to DNN 3.2.2.

Additional: this only happens when the roles were created on one portal, a template created, a new child portal created from the template, then any (non-default) roles that came with the template when added to the user automatically default an expiry date of one month ago today. Weird, can anyone help?

Thanks for your response. More research and in duplicating the condition - found that this only occurs when a child portal has been created from a template where the roles (other than the DNN defaults) that were created in the template site are susequently added to a user via manage roles for this user. I can manually create the roles in the new child and no problem but that defeats the purpose of templating. I would be interested if anyone can duplicate this problem or give me any ideas on what to check next.

When you created that template what version were you using?
Can you post here ther <role> section of the template for the roles that are giving you problems.
I'm sure I've seen that behaviour but cannot reproduce it right now, maybe it was something on previous versions that was corrected recently.

---

Vicenç Masanas
Banyoles, Girona - Spain