I have a formatted search used in my Motion Web.
%SEARCH{ ".*"
topic="ConfigOption*"
casesensitive="on"
regex="on"
nosearch="on"
nototal="on"
order="formfield(Option)"
excludetopic="ConfigOptionTemplate, ConfigOptionForm"
format="| [[$topic][$formfield(Option)]]| Values: $formfield(Range)<br />Default: $formfield(Default) | $formfield(Description) |"}%
The formfield "Default" is a default value for a Motion option.
It is sometimes numbers and sometimes text. So it is defined as a text field in the form.
When the value happens to be 0 the $formfield(Default) returns nothing instead of the 0. That is a bug and it worked in Cairo.
KJL
Can you demonstrate with a testcase please? It makes debugging much faster if I don't have to generate a testcase as well. Thanks.
CC
I will try and use this topic as test case abusing the ExtensionName field for it. Please bear over with me if I update this report many times in a row.
In the above search the result should be Value: Value_from_ExtensionName_field
If you put any value other than '0' it works. Example '2' or 'Crawford is a pain in the ass'. If you put '0' with no extra spaces after it the search returns nothing. It should show 0.
KJL
OK, thanks.
SVN 9107, 9108 (merged)
CC
Closed with the release of 4.0.2
KJL