3817: Profile.extra_data is null by default, but assumed to be a valid dictionary in the admin UI
- Duplicate
- Review Board
chipx86 | |
|
|
April 17, 2015 | |
What version are you running? 2.0.x What's the URL of the page containing the problem? /admin/ What steps will reproduce the problem? 1. Have a Profile with extra_data=null (as per the schema) 2. Visit /admin/ What is the expected output? What do you see instead? The page will crash, since it treats extra_data as a valid dictionary. We need to sanity-check this before accessing it. Should be a simple fix.