Ajax Search Pro - Live WordPress Search & Filter Plugin 4.26.16

Fixes

• Tablet item height for isotopic results is now correctly passed
• Redirection to first results on enter key and magnifier events corrected
• Duplication of search instances is now working again
• Autocomplete & Suggestions – Post categories are now possible to use as source
• User results – HTML properly stripped and removed, and description context enabled
• Post Type Filters – correctly memorized when redirecting to the results page
• Minor Typo fixes
• Language files updated

Added

• Separate Mobile, Tablet and Desktop search box width, and isotopic result width/height options
• Results information box – it is now possible to display the phrase entered and the number of results found on top of the results list
• get_asp_result_field($field) & the_asp_result_field($field) functions – Can be used in search.php theme file, within the loop. It returns the search result fields (such as the image, relevance etc..), that are exclusive to Ajax Search Pro.

Changes

• ‘asp_init_search_bar’ event added, triggers when a search bar is initialized
• [multisite] – Search instances are assigned ownership, and only the assigned admin or super admin can access them. (old search instances are assigned to ‘anyone’ in the admins group, super admin can change them)
• PODs – Tested for Custom PODs relation to Post type extensions – searchable via the Index Table
• Back-end UI improvements #1 – some inputs have changed, so that they automatically resize based on the input size.
• Back-end UI improvements #2 – updates to option descriptions & more intuitiveness improvements

Fixes

• String translations for custom field filter values are now registered properly
• Back-end: Options now correctly save when the server has a very low max_input_vars setting (<500) in effect, via a parse_str wrapper
• Isotopic results – better & faster mobile orientation and browser resize event handling during displaying paginated results.
• (ignored, not an issue) Post Format label is now available on the display mode list, under the taxonomy term filters panel
• Search in ‘private’ posts is now only visible for users above editor capabilities
• Theme Loader – Now properly resets some custom stylings
• Custom Field Filters – Multi-select options now have an adjustable logic, just like checkboxes
• The ‘No results’ and ‘Did you mean?’ back-end options now accept HTML tags.

Added

• Gutenberg editor modules & compatibility test & WordPress 5.0 compatibility tested
• New theme group – Max UI (instead of curvy)

Changed

• Themes – Input background changes, on some themes, the input field background changed to transparent, to aviod confusion with the overall box background.
• When tables are not created, the plugin now outputs the generated SQL and instructions to execute it in order to create the tables properly.
• Advanced fields – Taxonomy syntax accepts more parameters: hide_empty, childless, hierarchical
• Index Table – Now re-tries failed index queries, expecting a much fluid indexing process

Fixed

• Custom field date filter – ACF date field choice no longer displays an information message (yymmdd), as it is incorrect. (it works correctly)
• Advanced fields – ACF choice field labels are displayed, when the field return mode is set to ‘Both’ (array)
• Content type filter – ‘comments’ content type added, moved from the Generic filters section
• “No results” bug – container no longer displayed when loading ‘more results’ (due to inaccurate or unset results count)
• More results – no longer displayed, when clicking the close (x) icon, and re-entering the same phrase again
• Date filter – the date picker now appears correctly on the back-end
• More robust https detection, as in some cases incorrectly configured site URLs resulted in wrong protocol urls
• Priority saving issue fix – affecting Multitisites only
• User exclusion – now working with all/anonymous user options
• Index table engine – Fixed a query format, when using the ‘OR’ keyword logic
• Custom field checkboxes filter – fixed and issue where the ‘Exactly LIKE’ operator would not work correctly