I am trying to:
Display a Calendar Field "Completion Date" if and only if a preceding Checkbox "Completion Date - X" has been checked.
- Set a value of: "Date" in the "Value to Store" section of the "Completion Date - X" Checkbox
- Used the Conditional Code: ($(completion-date-x) eq Date) in the "Completion Date" Calendar Field
The Calendar Field "Completion Date" always shows up whether or not "Completion Date - X" has been checked.
Other Checkbox fields with similar conditional display logic work perfectly using similar settings.
Link to a page where the issue can be seen:
hidden link
I expected to see:
No Calendar Field "Completion Date" when Calendar Checkbox "Completion Date - X" remained unchecked.
Instead, I got:
A visible Calendar Field in the Custom Post Creation Screen when the Calendar Checkbox remained unchecked.
Hi Andrew,
Thank you for contacting us and I'll be happy to assist.
During testing, I was able to reproduce this issue on my test website as well.
When a repeating field group is showing in the "horizontal" view, the date field is visible on the page load, even if a condition exists to hide it. It does hides/show correctly if the connected checkbox is changed after the page has loaded.
Appreciate you brought this forward and I’ll report this limitation to our concerned team. We’ll get back in touch, as soon as there is an update.
As a quick fix, you can switch to the "vertical" view while editing content and you'll note that the date field will only show when the related condition is true ( screenshot: hidden link ).
I hope this helps and please let us know if you need any further assistance.
regards,
Waqar
Thanks so much Waqar,
I'm glad the bug was identified and I look forward to the patch coming out - it's not a big deal in terms of the data entry function but it will be great when that condition is functioning properly in all views.
I really appreciate your prompt and detailed response as well as the commitment to forward the issue to your development team.
Thanks!
Hi Andrew,
Just wanted to follow up and update you, that the fix for this issue, is set to be included in the next major release ( Types v3.2 ).
Thank you for your report and patience.
regards,
Waqar
Hi Andrew,
Thank you for waiting and just wanted to update that Types 3.2 has been released, which addresses the issue from your report.
regards,
Waqar