FacetWP 4.4 was released on April 23, 2025. This update contains the following improvements, new features and bug fixes:

New Map and Proximity facets

This update brings FacetWP up-to-date with the latest Google Maps developments. It comes with significant changes that affect both the Proximity facet and the Map facet.

Make sure to read the news article about the Map/Proximity part of the release. It explains in detail what has changed, why we are doing this, why you should consider migrating to the new versions, and which migration steps to follow exactly.

Other Map facet improvements

Besides the above-mentioned new Google Maps integration and all related changes, we fixed a few other issues in the new Map facet (not in the legacy Map facet add-on):

  • We fixed a bug with large/wide infowindows opening partly or entirely outside the map viewport when the clicked marker was close to the map’s viewport edge. This issue only happened with the “Info window ajax loading” setting enabled. To prevent this, markers/infowindows are now automatically repositioned when this happens, and will open fully within the map viewport.
  • Using the browser’s back button when using the map was causing unexpected marker/cluster results and counts, or an unfunctional map. Using the back button now works, also when the “Enable map filtering” button is enabled.

    • Accessibility improvements

    We fixed an accessibility bug in fSelect facets that caused the aria-checked attribute value to not be updated to true when an option was selected.

    Slider facet handles now have an aria-label attribute for accessibility. The label value is lower for the lower handle and upper for the upper handle. These two labels can be changed or translated with the facetwp_18n hook.

    Improved debugging of hooks used

    How to use FWP.settings.debug.hooks_used in the browser console to track the usage of hooks.
    How to use FWP.settings.debug.hooks_used in the browser console to track the usage of hooks.

    With Debug Mode enabled in FacetWP’s settings, typing FWP.settings.debug.hooks_used in the browser console will list all relevant hooks that are in use on the page, with their file name and line number.

    The listed hooks are all hooks with a name that starts with facetwp, and the pre_get_posts hook.

    To be better able to track issues with post results (as output by any WP_Query) being manipulated by custom code or other plugins, FacetWP v4.4 adds the posts_results hook to this list of detectable hooks.

    We also added a new FacetWP hook, facetwp_debug_hooks, that makes it possible to add any other hook to the list of detectable hooks. You could use this to track the usage of any hook and quickly find the corresponding file and line number.

    Improved Hierarchy facet

    The Hierarchy facet gained a few improved features:

    Changed default indexed value for ACF True/False fields

    We changed the indexing of the default value of ACF True/False fields. In previous versions, without the field having its “Default Value” setting enabled, this field type was being indexed as false for posts without a saved field and posts that do not have this field.

    We changed this behavior so that a default value is now only indexed when explicitly set, by enabling the “Default Value” in the field’s settings. In this case, the default value is indexed as true for posts without a saved field and posts that do not have this field.

    If you need to set or keep a default value of false, you can do so with this new hook:

    How to use custom PHP code?
    PHP code can be added to your (child) theme's functions.php file. Alternatively, you can use the Custom Hooks add-on, or a code snippets plugin. More info
    add_filter( 'facetwp_index_acf_truefalse_default_false', '__return_true' );

    See this section for an extended explanation.

    Note that we recommend not setting a default value, to prevent the indexing of this field for all posts in your site without a saved field, and post types that do not even have that field. In large sites, this can lead to a lot of unnecessary database rows.

    Other fixes and improvements

    • We fixed a bug that caused WooCommerce breadcrumbs to incorrectly add “/ Page 1” when loading a page with a facet selection, or when using the facetwp_preload_url_vars hook. The fix prevents “/ Page x” being added to the breadcrumbs at all when facets are active on a WooCommerce product page.
    • We fixed a bug in the Color facet which caused it have a missing Facet Logic setting since FacetWP v4.3.5.
    • We fixed a PHP warning that happened when indexing WooCommerce variations, when a facet value has no parent term set.
    • We fixed a bug that happened when a facet had its Value modifiers setting set to any value other than “Off”, with no actual values entered in its field. In this case, the facet was being indexed as if there were value modifiers present, leading to an empty facet. We added a check for value modifiers being empty or containing only spaces, in which case the setting is ignored.
    • We fixed a bug that happened when indexing facets that have an Advanced Custom Fields Taxonomy field as data source. In this case, the facet did not re-index and update its choices when the taxonomy terms were changed or deleted. Note that in general, it is recommended to use the taxonomy itself as the facet’s data source, instead of an ACF Taxonomy field.
    • In all facets with this setting, “Preserve ghost order” is now hidden when “Sort by” is set to “Highest count”. This change was made because when ordering by highest count, the ghost order is ignored.
    • We updated all language strings and translations, and added a Text Domain and Domain Path heading, so that the front-end fwp-front text domain is now automatically recognized in translation plugins like Loco Translate.

    See also

    Last updated: April 25, 2025