| |
@@ -431,8 +431,8 @@
|
| |
|
| |
def __init__(self, name, description, default_value=False,
|
| |
readonly=False):
|
| |
- # The db stores 1/0. Convert the passed-in value if
|
| |
- # necessary
|
| |
+ # We're not too picky about what data we get, but we make sure it's a
|
| |
+ # boolean by the time we're done with it
|
| |
if default_value in [u'1', 'True', True]:
|
| |
default_value = True
|
| |
else:
|
| |
@@ -442,7 +442,11 @@
|
| |
readonly=readonly)
|
| |
|
| |
def import_value(self, value):
|
| |
- self._assigned_value = value
|
| |
+ # Convert the text string stored in the database back to a boolean
|
| |
+ if value == 'True':
|
| |
+ self._assigned_value = True
|
| |
+ elif value == 'False':
|
| |
+ self._assigned_value = False
|
| |
|
| |
|
| |
class ConfigHelper(Log):
|
| |
merlinthp
commented 7 years ago
All options types are stored as strings in the backend database. The
Condition config option type is a subclass of the Pick option that has
only the Python True and False values as valid values. When a specific
value for the option is stored into the database, this is rendered into the
text strings 'True' or 'False'. When the option is loaded back from the
database, it remains a string. This causes the issue that any "it option"
style checks will always evaluate to true. This manifests in the plugin
configuration pages, where the checkboxes for Condition options are always
checked, even if the value is set to false in the database.
This patch adds code to the Condition import_value function to coerce the
strings into Python bools.
The authfas plugin has a Condition option that it tries to use the value of
as a string, so convert that to a boolean operation.
Signed-off-by: Howard Johnson merlin@merlinthp.org