I'm not sure if this is related to the other issue we had in the ticket "Radio Group no Longer Showing in View", but we noticed that a date range filter that used to work in Views is no longer working after the last update.
We have a View that has a FROM and TO date filter (see image 1) and we're seeing that when we have both dates in there (from & to), only 1 of the dates get added to the URL, and so the search doesn't work.
For example, in image 2, we set the FROM date and clicked SEARCH, and the date wasn't put in the URL and the results weren't properly filtered.
When we remove the TO date from the View, then the FROM date is properly put in the URL. When both dates are in the View, only the last one (the TO date) is put in the URL and filtering the results.
Can you please confirm if this is an issue, and if it will soon be fixed.
This is the code in the View:
<div class="col-sm-4">
<!-- date recorded from -->
<div class="form-group">
[wpml-string context="wpv-views"]By date recorded range. FROM:[/wpml-string]
<div class="gf-vid-search-date-bk gf-vid-search-input-text">
[wpv-control-postmeta field="wpcf-_gf_date_recorded" url_param="wpv-wpcf-_gf_date_recorded_min"]
</div>
</div>
</div>
<div class="col-sm-4">
<!-- date recorded to -->
<div class="form-group">
[wpml-string context="wpv-views"]TO:[/wpml-string]
<div class="gf-vid-search-date-bk gf-vid-search-input-text">
[wpv-control-postmeta field="wpcf-_gf_date_recorded" url_param="wpv-wpcf-_gf_date_recorded_max"]
</div>
</div>
</div>
Hello. Thank you for contacting the Toolset support.
It looks like the same issue about the range filters not working and this is known to us.
Our Devs shared a hotfix that will help you to fix this issue. You should download the hotfix file "wpv-filter-meta-field-embedded.php" and replace it at the path:
=> plugins/wp-views/embedded/inc/filters
Download link:
=> hidden link
Can you please confirm the hotfix shared help you to resolve your issue.
I would like to inform you that the latest release of Toolset Views 3.0.2, includes a fix for this issue. Please feel free to update the Toolset Views plugin on your install.