Settings API does not parse incoming values
The api saves setting's value as a string independently of the setting type. This can cause unexpected errors when the value bubbles through to a place where string is not expected.
#1 Updated by Tomáš Strachota almost 9 years ago
- Status changed from Assigned to Ready For Testing
#2 Updated by Dominic Cleal over 8 years ago
- Legacy Backlogs Release (now unused) set to 10
#3 Updated by Anonymous over 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 225b381805419ca6a393833f83f18d78f0ce187b.
Fixes #6285 - Settings API does not parse incoming values to correct data type