What steps will reproduce the problem?
1.Have a character with a profile which is not the one that would have been chosen/created for that character as a default on their first login.
2.From another character, delete that profile.
3.Log into the character from step 1.
What is the expected output? What do you see instead?
Expected behavior is that the profile for the character would be the default (however that was configured by the third param of AceDB:New) as if they were logging in for the first time with that character. Instead, they have a profile with default values (as per second param) with the same name as what they had before, meaning the DeleteProfile operation was instead, effectively, just a Reset.
Please provide any additional information below.
To fix this, AceDB:DeleteProfile should loop through the profileKeys table and delete any entries whose value matches the name of the profile that has been deleted.
- 1 comment
- Last updated
- Sep 13, 2013
- Jan 06, 2013
- Fixed - Developer made requested changes. QA should verify.
- Defect - A shortcoming, fault, or imperfection
- Medium - Normal priority.