I have tested this item ✅ successfully on 827839f

I have tested this item ✅ successfully on 827839f

Ready to Commit after two successful tests.

@C-Lodder can you please respond to the question from @laoneo and then we can move forward with this.

Honestly I would revert all the === '' checks as they need to be checked on a case by case basis, because it can have unwanted side effects.

About strict comparison in template files (of custom fields)

Are you sure we do not break here something as 0 and false are allowed now? Same for the others where you do === ''.

Actually this change will allow an integer value of 0 (zero)
because current comparison is unable to display zero (i mean the integer type of zero)

but then you would ask, why currently display of zero is possible ? (i mean currently it works)

It is because currently fields like

• text, textarea, integer fields
  use default handling for values (they do not implement some custom handling before passing to the value to the template),
  which passes to the template file (/tmpl/*.php) a string value

That is this is passed

• string(1) "0"

thus this if (string(1) "0" == '') evaluates to false, thus display of zero is possible

The strict comparison will effect the case of passing a value NULL or FALSE
since it will allow them to be "displayed"
but then current template code for such value will show nothing anyway
aka the current display of fields will not change

@laoneo @brianteeman all the == '' have been reverted as request. Please squash the commits

Thanks