Forums › Forums › Search & Filter Pro › ACF Form Field Not Showing Results
- This topic has 7 replies, 2 voices, and was last updated 5 years, 4 months ago by
Trevor.
-
Anonymous(Private) October 28, 2019 at 2:42 pm #224800
Strange behavior we’re experiencing. Two filters in question, one works properly the other does not when managing same data.
Filter 1 (works): It is using the ‘Post Meta’ area with ‘Only return results which match specific post meta data’ and have it restricted to a ACF field that has posts checked for this field. This form returns results for the posts that have the field in question checked. This is using shortcode [searchandfilter id=”7723″ show=”results”]
Filter 2 (doesn’t work): The form for this filter is using a widget for the form.(Tested it as just shortcode and still doesn’t work) All posts appear on this results page, to begin. When the same ACF field (as in the above filter) in the form is checked, no results appear. We know products have this checked.
We’ve updated cache several times on both search filters without luck.
Thanks for any guidance.
Trevor(Private) October 29, 2019 at 2:25 pm #224982One problem that I can see is that you have customised the results.php file, but both forms are set to use Infinite Scroll, and I think you customised the standard results.php content.
In the plugin/templates folder you will find an infinite scroll version. You need to use the contents of that instead, but the file must still be named results.php
I am far from sure that is the problem, but that does need fixing first. Note the names of the divs in that file. If you change them (
search-filter-results-list
andsearch-filter-results-list
), you must complete the fields in the form settings with what you have used.Trevor(Private) October 30, 2019 at 3:37 pm #225132Ah. You aren’t going to want to hear this then. Another user, it turns out, had this issue a few days ago (not one of my tickets). It turns out our plugin always converts the key name to lower case, so that is why what you saw happened. This has been fixed in the forthcoming release (2.4.7).
Anyway, for now, thanks for letting me know. I will close this thread for now.
-
AuthorPosts