Object caching
In most cases, using FacetWP in combination with (persistent) object caching is problematic.
We have seen some users using it successfully with FacetWP. But most often it interferes with FacetWP’s ability to detect or use the right query on refresh. This leads to a range of possible issues like post listings not refreshing or filtering, facets not loading, unexpected posts showing, pagination issues, wrong post and/or result counts, or the “FacetWP was unable to auto-detect the post listing” error. These issues may depend on the exact implementation of the object cache (by yourself or the hosting company), or the caching plugin used. We are investigating why it sometimes works and other times not, and whether there is a general solution or a fix for specific implementations or plugins. If there is any new information, we will update this page.
Depending on the implementation or plugin used, you may be able to exclude your facet URL/page, or its cache groups from being cached. The only other solution for now is to disable object caching entirely.
If you have implemented object caching successfully with FacetWP, or have found a fix for specific setups, please let us know so we can research the plugins/settings used.
Solutions for specific hosting providers
WP Engine
If you are hosting your site on WP Engine, you can turn off WP Engine’s object cache in the settings.
Pressable
Pressable uses several layers of caching. Two of these caching types appear to be problematic on pages with facets: the “Batcache” page cache, and the (persistent) object cache. See our Pressable page for more info and ways to exclude your facet page(s) from these two types of caching.