If, in the same form, you mixed in your custom required functions the current (return 'show' and 'required' info) approach and the legacy (only return 'required' info) approach, you could get unexpected results: a field could be hidden by DaDaBIK even if it was supposed to be displayed.
The bug will be fixed in the next release of DaDaBIK. The only workaround at the moment is to change your custom required functions so that they all use the current
(return 'show' and 'required' info) approach.
If there is any update on this bug, it will be posted here.
Best,
The bug will be fixed in the next release of DaDaBIK. The only workaround at the moment is to change your custom required functions so that they all use the current
(return 'show' and 'required' info) approach.
If there is any update on this bug, it will be posted here.
Best,
