I'm using a fairly old version of this module (2.2) due to being stuck with dotnetnuke 3.2.2 on a particular clients website. But here's the issue anyway...
I need users to be able to change their usernames, so I've set the "users can change username" flag on. After some testing I figured this option works by simply creating a new dnn account with the new username, and the remaining user fields are transferred to the new account.
This works ok except that only fields linked to core dnn fields are retained. Effectively a new user account is created with the new username, and any linked core dnn fields are also populated, but the original data in the "DynamicRegistration_QuestionResponse" table remains linked to the old user ID. This means all user fields that are not linked to core dnn fields are lost as they now reference a user id that no longer exists.
I'm guessing that this has probably been fixed in later versions of the module, but I'm restricted to whatever version of this module that still works on DNN 3.2.2.
Is there a fix/update that I could use for my dnn 3.2.2 site, or am I going to have to fix this one myself given the old version of the module and dnn I'm using?
Thanks
Steve