few (strange) issues with storing/getting null in float field

[valan]

There is FieldtypeFleat field "my_float_field" with setting "Blank and Null have different meanings". I have few (strange) issues with it.

(1) Issue number 1

When I want to store null in this field, it doesn't save (or return) null. I want to get null back when I save null and 0 when I save integer 0. What's wrong here?

$value = null;
echo 'Type=' . gettype($value) . ' Value=' . print_r($value, true));
$page->setAndSave('my_float_field', $value);
echo 'Type=' . gettype($page->my_float_field) . ' Value=' . print_r($page->my_float_field, true));
echo 'Type=' . gettype($page->my_float_field) . ' Value=' . print_r($page->getUnformatted('my_float_field'), true));

// Result:
Type=NULL Value =
Type=double Value = 0
Type=double Value = 0

(2) Issue number 2

This field has Visibility=Open+Closed when blank+Locked

If I save null in this field, it disappearas from page edit admin. If there is some value - it shows it normally... If I change setting "Blank and Null have different meanings" to "... equivalent" it also does not help. This looks like either bug or some db issue. I've checked field settings in db and didn't find any strange things there... so tend to think that it is bug. Or I don't understand smth... Please help.

 

 

[LostKobrakai]

Part 2 is probably because visibility settings are evaluated in js only, which ultimately doesn't know anything about the setting of the field.

[Robin S]

5 hours ago, valan said:

There is FieldtypeFleat field "my_float_field" with setting "Blank and Null have different meanings".

There's no such setting is there? I think you mean "Blank and 0 have different meanings", which doesn't promise anything about blank and null being treated differently. I guess PW treats these as equivalent, which explains issue 2 also.

[valan]

28 minutes ago, Robin S said:

There's no such setting is there? I think you mean "Blank and 0 have different meanings", which doesn't promise anything about blank and null being treated differently. I guess PW treats these as equivalent, which explains issue 2 also.

Yes, Blank and 0 have different meaning. I guess Blank for float = Null. Anyway, hiding field if it's value is null is not expected behavior I think.