Posted By Bill Witham on 28 Jun 2019 11:17 AM
I'm attempting to use an RSVP Code for a Role to allow users to use this code to auto assign the role to them. However, what I have found is that when the role is assigned using this approach the role expiry date is set to the date it was assigned.
The thought is that maybe it is attempting to set the start date to this but instead it is setting the expire date.
Is this a bug/defect with the RSVP functionality?
I also posted this same question here - https://www.dnnsoftware.com/answers...latform-93
Yes, this is a bug. I've run into this myself. As a workaround for a client, we had to build a standalone module that allows them to manage this aspect of security roles. The bug is part of the API. Basically, you need to create the role and RSVP code, then update the role again to fix the expiration date.
It looks like Daniel Valadas has already reported this issue too. :)